Thread (22 messages) 22 messages, 5 authors, 2026-02-10

Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair

From: Wolfram Sang <wsa+renesas@sang-engineering.com>
Date: 2026-02-10 10:44:28
Also in: linux-arm-msm, linux-doc, linux-gpio, linux-iio, linux-omap, linux-remoteproc, linux-renesas-soc, linux-spi, linux-sunxi

Hi Andy,
quoted
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.

I'll start with some cleanup in some minutes.

Happy hacking,

   Wolfram

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help