From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Hanne-Lotta Mäenpää" <hannelotta@gmail.com>,
mchehab@kernel.org, ribalda@chromium.org, hverkuil@xs4all.nl,
hljunggr@cisco.com, dave.jiang@intel.com, jgg@ziepe.ca,
saeedm@nvidia.com, Jonathan.Cameron@huawei.com, corbet@lwn.net,
mario.limonciello@amd.com, W_Armin@gmx.de,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
linux-media@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH 3/4] docs: Improve grammar in Userspace API/fwctl
Date: Mon, 19 May 2025 16:01:11 +0300 (EEST) [thread overview]
Message-ID: <264386b3-075d-ef1d-e3b2-9a2937ca05cb@linux.intel.com> (raw)
In-Reply-To: <aCqKNg3p_VlGbce_@archie.me>
[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]
On Mon, 19 May 2025, Bagas Sanjaya wrote:
> On Sat, May 17, 2025 at 04:27:10PM +0300, Hanne-Lotta Mäenpää wrote:
> > Fix typos and improve grammar in the documentation for
> > fwctl subsystem.
> >
> > Use the word user space consistently, instead of having
> > two variants (user space vs. userspace).
> >
> > Change wording of denied behaviour to be disallowed
> > behaviour when describing the interface.
> >
> > Signed-off-by: Hanne-Lotta Mäenpää <hannelotta@gmail.com>
> > ---
> > Documentation/userspace-api/fwctl/fwctl.rst | 30 ++++++++++-----------
> > 1 file changed, 15 insertions(+), 15 deletions(-)
> >
> > diff --git a/Documentation/userspace-api/fwctl/fwctl.rst b/Documentation/userspace-api/fwctl/fwctl.rst
> > index fdcfe418a83f..a74eab8d14c6 100644
> > --- a/Documentation/userspace-api/fwctl/fwctl.rst
> > +++ b/Documentation/userspace-api/fwctl/fwctl.rst
> > @@ -54,7 +54,7 @@ operated by the block layer but also comes with a set of RPCs to administer the
> > construction of drives within the HW RAID.
> >
> > In the past when devices were more single function, individual subsystems would
>
> Do you mean that devices used to be singleton in its functionality? Or having
> multiple functions?
>
> > -grow different approaches to solving some of these common problems. For instance
> > +grow different approaches to solving some of these common problems. For instance,
> > monitoring device health, manipulating its FLASH, debugging the FW,
> > provisioning, all have various unique interfaces across the kernel.
> >
> > <snipped>...
> > 3. Write access to function & child debug information strictly compatible with
> > the principles of kernel lockdown and kernel integrity protection. Triggers
> > - a kernel Taint.
> > + a kernel taint.
>
> Improving grammar includes s/Taint/taint/?
>
> Confused...
To be fair, the changelog also said "Fix typos". So Bagas, do you mean
"Taint" should be always capitalized? At least this doesn't support
that position:
git grep -i taint Documentation
--
i.
next prev parent reply other threads:[~2025-05-19 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 13:27 [PATCH 1/4] docs: Improve grammar in Userspace API/DVB API Hanne-Lotta Mäenpää
2025-05-17 13:27 ` [PATCH 2/4] docs: Improve grammar, formatting in Video4Linux Hanne-Lotta Mäenpää
2025-05-18 8:08 ` Jonathan Corbet
2025-05-19 1:23 ` Bagas Sanjaya
2025-05-21 15:17 ` Hanne-Lotta Mäenpää
2025-05-21 15:12 ` Hanne-Lotta Mäenpää
2025-05-17 13:27 ` [PATCH 3/4] docs: Improve grammar in Userspace API/fwctl Hanne-Lotta Mäenpää
2025-05-19 1:32 ` Bagas Sanjaya
2025-05-19 13:01 ` Ilpo Järvinen [this message]
2025-05-21 2:48 ` Bagas Sanjaya
2025-05-21 15:38 ` Hanne-Lotta Mäenpää
2025-05-17 13:27 ` [PATCH 4/4] docs: Fix typos, improve grammar in Userspace API Hanne-Lotta Mäenpää
2025-05-19 1:24 ` Bagas Sanjaya
2025-05-19 1:49 ` Mark Pearson
2025-05-19 1:34 ` [PATCH 1/4] docs: Improve grammar in Userspace API/DVB API Bagas Sanjaya
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=264386b3-075d-ef1d-e3b2-9a2937ca05cb@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=W_Armin@gmx.de \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=hannelotta@gmail.com \
--cc=hljunggr@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=jgg@ziepe.ca \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mchehab@kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=ribalda@chromium.org \
--cc=saeedm@nvidia.com \
/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