[RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair
Andy Shevchenko
andriy.shevchenko at intel.com
Tue Feb 10 07:14:04 PST 2026
On Tue, Feb 10, 2026 at 11:44:25AM +0100, Wolfram Sang wrote:
> > > And if so, would be this series acceptable
> > > as-is then (modulo the better include-sorting mentioned by Andy)?
> >
> > *From my experience it's not the Q "will they or not?", the Q is "when?"
> > they start abusing it. I really prefer to hide as much as possible from
>
> I totally agree with you on that.
>
> > day 1. Maybe the structure can be split to two? Currently IIO has a
>
> I also thought that keeping some internal header might provide that
> safety. When looking into it, I didn't see an obvious and somewhat
> elegant way. Even more, I got a better picture of why Bjorn named the
> current approach "unergonomic". I got some ideas which look doable in my
> time frame. I will try going the full route, after all.
Thanks!
Looking forward for the rest, the cleanup is quite good, no added lines.
--
With Best Regards,
Andy Shevchenko
More information about the linux-arm-kernel
mailing list