From: Mark Brown <broonie@kernel.org>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Naresh Solanki <naresh.solanki@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Documentation: ABI: sysfs-driver-regulator-output
Date: Tue, 12 Sep 2023 15:00:09 +0100 [thread overview]
Message-ID: <9630368c-fb8a-4e7e-85a6-e7f946a3b551@sirena.org.uk> (raw)
In-Reply-To: <1518370c-e0cd-4d78-af54-3e2cf4dd6e3c@hatter.bewilderbeest.net>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Sun, Sep 10, 2023 at 01:50:37PM -0700, Zev Weiss wrote:
> On Mon, Sep 04, 2023 at 05:24:31AM PDT, Mark Brown wrote:
> > It's a clear on read interrupt.
> Sure, analogous behavior in hardware is reasonably common, but that doesn't
> strike me as a very compelling reason to design the kernel<->userspace
> interface to mimic it -- providing nicer interfaces than the raw hardware is
> one of the main reasons for having an OS in the first place, after all.
If it were something other than the userspace consumer I'd be more
worried, with this interface it's all sharp edges on a very embedded
system so it's a bit less concerning. In any case the obvious fix here
is to use clear on read.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-12 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 12:14 [PATCH 1/3] regulator: Add uapi header Naresh Solanki
2023-08-31 12:14 ` [PATCH 2/3] regulator: userspace-consumer: Add regulator event support Naresh Solanki
2023-09-01 9:27 ` Zev Weiss
2023-09-01 12:18 ` Mark Brown
2023-08-31 12:14 ` [PATCH 3/3] Documentation: ABI: sysfs-driver-regulator-output Naresh Solanki
2023-09-01 9:13 ` Zev Weiss
2023-09-03 13:04 ` Greg Kroah-Hartman
2023-09-04 0:48 ` Zev Weiss
2023-09-04 12:24 ` Mark Brown
2023-09-10 20:50 ` Zev Weiss
2023-09-12 14:00 ` Mark Brown [this message]
2023-09-12 14:03 ` Mark Brown
2023-09-20 9:02 ` Zev Weiss
2023-09-20 9:29 ` Greg Kroah-Hartman
2023-09-20 10:44 ` Zev Weiss
2023-09-20 10:48 ` Greg Kroah-Hartman
2023-09-20 10:53 ` Zev Weiss
2023-08-31 12:35 ` [PATCH 1/3] regulator: Add uapi header Mark Brown
2023-08-31 18:34 ` Naresh Solanki
2023-09-01 12:17 ` Mark Brown
2023-08-31 13:50 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9630368c-fb8a-4e7e-85a6-e7f946a3b551@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=zev@bewilderbeest.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®