From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "james.smart@broadcom.com" <james.smart@broadcom.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH] nvme-fc: Few trivial spelling fixes
Date: Tue, 23 Mar 2021 01:33:20 +0530 [thread overview]
Message-ID: <YFj4CKnnRg5lzN9K@ArchLinux> (raw)
In-Reply-To: <BYAPR04MB4965A5E081F84BA874957F3186659@BYAPR04MB4965.namprd04.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 415 bytes --]
On 18:36 Mon 22 Mar 2021, Chaitanya Kulkarni wrote:
>On 3/20/21 13:45, Bhaskar Chowdhury wrote:
>> s/boundarys/boundaries/ ..... two different places
>> s/assocated/associated/
>> s/compeletion/completion/
>> s/tranferred/transferred/
>> s/subsytem/subsystem/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>
>Patch looks fine but commit log could be better.
>
This is the best I could produce.
>
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-03-22 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 20:30 [PATCH] nvme-fc: Few trivial spelling fixes Bhaskar Chowdhury
2021-03-20 22:37 ` Randy Dunlap
2021-03-22 18:36 ` Chaitanya Kulkarni
2021-03-22 20:03 ` Bhaskar Chowdhury [this message]
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=YFj4CKnnRg5lzN9K@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).