[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <763bd845-d8d6-489c-bd31-305ed14bc40f@sirena.org.uk>
Date: Mon, 4 Sep 2023 13:24:31 +0100
From: Mark Brown <broonie@...nel.org>
To: Zev Weiss <zev@...ilderbeest.net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Naresh Solanki <naresh.solanki@...ements.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Documentation: ABI: sysfs-driver-regulator-output
On Sun, Sep 03, 2023 at 05:48:14PM -0700, Zev Weiss wrote:
> On Sun, Sep 03, 2023 at 06:04:23AM PDT, Greg Kroah-Hartman wrote:
> > But yes, reading a sysfs should almost never cause a side affect at all.
> > But what do you mean by "clear events?"
> I mean that when the sysfs file is read, the state variable whose value it
> exposes is also cleared as a side-effect (so the read operation "consumes"
> the value it returns) -- see the implementation in patch 2 of this series
> (specifically the 'data->events = 0' assignment in events_show()):
It's a clear on read interrupt.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists