From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Carlos Bilbao <bilbao@vt.edu>
Cc: 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 08:42:37 +0200 [thread overview]
Message-ID: <20210506084237.1f8363ba@coco.lan> (raw)
In-Reply-To: <2219636.ElGaqSPkdT@iron-maiden>
Em Wed, 05 May 2021 16:43:59 -0400
Carlos Bilbao <bilbao@vt.edu> escreveu:
> Fix the following typos in the Documentation/ABI/ directory:
>
> - In file obsolete/sysfs-cpuidle, change "obselete" for "obsolete".
>
> - In file removed/sysfs-kernel-uids, change "propotional" for "proportional".
>
> - In directory stable/, fix the following words: "associtated" for "associated",
> "hexidecimal" for "hexadecimal", "vlue" for "value", "csed" for "caused" and
> "wrtie" for "write". This updates a total of five files.
>
> - In directory testing/, fix the following words: "subystem" for "subsystem",
> isochrnous" for "isochronous", "Desctiptors" for "Descriptors", "picutre" for
> "picture", "capture" for "capture", "occured" for "ocurred", "connnected" for
> "connected","agressively" for "aggressively","manufacturee" for "manufacturer"
> and "transaction" for "transaction" and "malformatted" for "malformed". This
> updates a total of ten files.
>
> Signed-off-by: Carlos Bilbao <bilbao@vt.edu>
...
> 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".
On a quick look, it sounds that malformatted is valid, at least
in computing:
https://en.wiktionary.org/wiki/malformatted
https://etymologeek.com/eng/malformatted/73029882
https://en.glosbe.com/en/en/malformatted
Maybe the best here would be to double-check with PCI maintainers
and/or take a look at PCI specs and see what it is used there.
Thanks,
Mauro
next prev parent reply other threads:[~2021-05-06 6:42 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 [this message]
2021-05-06 13:31 ` Theodore Ts'o
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=20210506084237.1f8363ba@coco.lan \
--to=mchehab+huawei@kernel.org \
--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 \
/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