linux-kernel - Re: [PATCH] Fixed typos in all directories of Documentation/ABI/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210507101132.00003aeb@Huawei.com>
Date:   Fri, 7 May 2021 10:11:32 +0100
From:   Jonathan Cameron <Jonathan.Cameron@...wei.com>
To:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
CC:     Carlos Bilbao <bilbao@...edu>, <corbet@....net>,
        <hdegoede@...hat.com>, <gregkh@...uxfoundation.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fixed typos in all directories of Documentation/ABI/

On Thu, 6 May 2021 08:42:37 +0200
Mauro Carvalho Chehab <mchehab+huawei@...nel.org> wrote:

> Em Wed, 05 May 2021 16:43:59 -0400
> Carlos Bilbao <bilbao@...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@...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.

For reference, PCI specs make heavy use of malformed and very little
(possibly none) of malformatted.  However neither is used wrt to
VPD (that I can see anyway) so this info is largely irrelevant :)

> 
> Thanks,
> Mauro