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

[RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-25
[RFC PATCH 1/4] hwspinlock: refactor existing headers into provider.h · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-25
[RFC PATCH 2/4] hwspinlock: refactor existing headers into consumer.h · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-25
[RFC PATCH 3/4] treewide: convert hwspinlock users to the new consumer header file · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-25
Re: [RFC PATCH 3/4] treewide: convert hwspinlock users to the new consumer header file · Andy Shevchenko <hidden> · 2026-01-26
Re: [RFC PATCH 3/4] treewide: convert hwspinlock users to the new consumer header file · Mark Brown <broonie@kernel.org> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Andy Shevchenko <hidden> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Andy Shevchenko <hidden> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-27
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-02-09
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Andy Shevchenko <hidden> · 2026-02-09
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Bjorn Andersson <andersson@kernel.org> · 2026-02-09
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-02-09
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Bjorn Andersson <andersson@kernel.org> · 2026-02-09
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Andy Shevchenko <hidden> · 2026-02-10
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-02-10
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Andy Shevchenko <hidden> · 2026-02-10
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wilken Gottwalt <wilken.gottwalt@posteo.net> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Wolfram Sang <wsa+renesas@sang-engineering.com> · 2026-01-26
Re: [RFC PATCH 0/4] hwspinlock: refactor headers into public provider/consumer pair · Andy Shevchenko <hidden> · 2026-01-26

From: Andy Shevchenko <hidden>
Date: 2026-01-26 10:21:08
Also in: linux-arm-msm, linux-doc, linux-gpio, linux-iio, linux-omap, linux-remoteproc, linux-renesas-soc, linux-spi, linux-sunxi

On Mon, Jan 26, 2026 at 11:13:59AM +0100, Wolfram Sang wrote:

quoted

I don't like the idea of sharing internal stuff. Why would we need to have
a struct hwspinlock to be visible?

Providers need it, especially the 'priv' member. Consumers won't see it.

But can't we make it opaque?

We may have getters and setters for the priv member...

-- 
With Best Regards,
Andy Shevchenko

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help