From: "Theodore Ts'o" <tytso@mit.edu>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Carlos Bilbao <bilbao@vt.edu>,
corbet@lwn.net, hdegoede@redhat.com, Jonathan.Cameron@huawei.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixed typos in all directories of Documentation/ABI/
Date: Thu, 6 May 2021 09:31:03 -0400 [thread overview]
Message-ID: <YJPvl6Si9Xi0w5tG@mit.edu> (raw)
In-Reply-To: <20210506084237.1f8363ba@coco.lan>
On Thu, May 06, 2021 at 08:42:37AM +0200, Mauro Carvalho Chehab wrote:
>
> > diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
> > index ef00fada2efb..bfd017204563 100644
> > --- a/Documentation/ABI/testing/sysfs-bus-pci
> > +++ b/Documentation/ABI/testing/sysfs-bus-pci
> > @@ -139,7 +139,7 @@ Description:
> > binary file containing the Vital Product Data for the
> > device. It should follow the VPD format defined in
> > PCI Specification 2.1 or 2.2, but users should consider
> > - that some devices may have malformatted data. If the
> > + that some devices may have malformed data. If the
> > underlying VPD has a writable section then the
> > corresponding section of this file will be writable.
> >
>
> (not a native English speaker here)
>
> I'm in doubt about this one. The description is talking about the
> "VPD format".
Maybe "badly formatted" or to be more clear, "some devices may be
reported incorrectly forrmatted data"?
- Ted
next prev parent reply other threads:[~2021-05-06 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 20:43 [PATCH] Fixed typos in all directories of Documentation/ABI/ Carlos Bilbao
2021-05-05 21:10 ` Randy Dunlap
2021-05-05 22:25 ` Carlos Bilbao
2021-05-05 22:28 ` Carlos Bilbao
2021-05-05 22:54 ` Randy Dunlap
2021-05-06 6:42 ` Mauro Carvalho Chehab
2021-05-06 13:31 ` Theodore Ts'o [this message]
2021-05-06 14:54 ` Carlos Bilbao
2021-05-06 15:19 ` [PATCH v3] " Carlos Bilbao
2021-05-06 16:51 ` Mauro Carvalho Chehab
2021-05-13 13:30 ` Carlos Bilbao
2021-05-13 13:31 ` [PATCH v3.1] " Carlos Bilbao
2021-05-13 15:13 ` Jonathan Corbet
2021-05-07 9:11 ` [PATCH] " Jonathan Cameron
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=YJPvl6Si9Xi0w5tG@mit.edu \
--to=tytso@mit.edu \
--cc=Jonathan.Cameron@huawei.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
/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