From: Carlos Bilbao <bilbao@vt.edu>
To: corbet@lwn.net, hdegoede@redhat.com, mchehab+huawei@kernel.org,
Jonathan.Cameron@huawei.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
Stephen Hemminger <sthemmin@microsoft.com>,
Randy Dunlap <rdunlap@infradead.org>,
bilbao@vt.edu
Subject: Re: [PATCH] Fixed typos in all directories of Documentation/ABI/
Date: Wed, 05 May 2021 18:25:03 -0400 [thread overview]
Message-ID: <4341223.LvFx2qVVIh@iron-maiden> (raw)
In-Reply-To: <de6f22e2-3f3c-0ce3-a73d-fb881646f1e8@infradead.org>
Hello Randy,
Thank you for your quick feedback that I address below, I will send the patch
again after this email.
> > What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/cpu
> > Date: September. 2017
> > KernelVersion: 4.14
> > Contact: Stephen Hemminger <sthemmin@microsoft.com>
> >
> > -Description: VCPU (sub)channel is affinitized to
> > +Description: PCP (sub)channel is affinitized to
>
> Stephen- comment here?
Stephen, no need to comment. This was my fault, VCPU was already right. Fixed.
> > diff --git a/Documentation/ABI/stable/sysfs-class-infiniband
> > b/Documentation/ABI/stable/sysfs-class-infiniband index
> > 348c4ac803ad..bbaa7bab8af4 100644
> > --- a/Documentation/ABI/stable/sysfs-class-infiniband
> > +++ b/Documentation/ABI/stable/sysfs-class-infiniband
> >
> > @@ -140,7 +140,7 @@ Description:
> > by LocalPhyErrors
> >
> > excessive_buffer_overrun_errors: (RO) This counter, indicates an
> >
> > - input buffer overrun. It indicates possible misconfiguration of
>
> Above is correct AFAIK although my 3 quick dictionary searches didn't find
> it spelled either of those ways. :)
Also true, "misconfiguration" is accepted. Change removed.
>
> codespell find 4 problems here (in ABI/testing):
>
> $ codespell sysfs-devices-system-cpu
> sysfs-devices-system-cpu:100: internel ==> internal
> sysfs-devices-system-cpu:283: specificed ==> specified
> sysfs-devices-system-cpu:298: beyound ==> beyond
> sysfs-devices-system-cpu:535: Symetric ==> Symmetric
>
>
> Would you mind adding those to your patch?
>
Changes added to the patch.
next prev parent reply other threads:[~2021-05-05 22:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 20:43 Carlos Bilbao
2021-05-05 21:10 ` Randy Dunlap
2021-05-05 22:25 ` Carlos Bilbao [this message]
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
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=4341223.LvFx2qVVIh@iron-maiden \
--to=bilbao@vt.edu \
--cc=Jonathan.Cameron@huawei.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sthemmin@microsoft.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
all inboxes | Powered by JetHome®