From: R Veera Kumar <vkor@vkten.in>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Kershner <david.kershner@unisys.com>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: unisys: Documentation: Fix for longline and typo in doc
Date: Wed, 18 Mar 2020 06:03:27 +0530 [thread overview]
Message-ID: <20200318003325.GA1739@tulip.local> (raw)
In-Reply-To: <20200317110044.36940c33@elisabeth>
On Tue, Mar 17, 2020 at 11:00:44AM +0100, Stefano Brivio wrote:
> On Sat, 14 Mar 2020 11:01:51 +0530
> R Veera Kumar <vkor@vkten.in> wrote:
>
> > Fix longline and a typo in documentation.
> > Found using checkpatch.pl.
> >
> > [...]
> >
> > @@ -56,7 +56,7 @@ NOT covered in this document:
> > 2.1.1. Overview
> > ---------------
> >
> > -The visorbus driver handles the virtual busses on which all of the virtual
> > +The visorbus driver handles the virtual buses on which all of the virtual
>
> This is not a typo, both spellings are correct and you are anyway
> keeping a "busses" in the other section. We also
> have drivers/i2c/busses/. If checkpatch is reporting this, I think it
> should be fixed.
>
English US spells busses.
English Uk spells buses.
The dictionary database used by checkpatch.pl, codespell is the problem.
> Please re-send.
>
Sent it.
Veera
> --
> Stefano
>
next prev parent reply other threads:[~2020-03-18 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 5:31 [PATCH] staging: unisys: Documentation: Fix for longline and typo in doc R Veera Kumar
2020-03-17 10:00 ` [Outreachy kernel] " Stefano Brivio
2020-03-18 0:33 ` R Veera Kumar [this message]
2020-03-18 23:09 ` Stefano Brivio
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=20200318003325.GA1739@tulip.local \
--to=vkor@vkten.in \
--cc=david.kershner@unisys.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sbrivio@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.