From: "John Stoffel" <john@stoffel.org>
To: antlists <antlists@youngman.org.uk>
Cc: John Stoffel <john@stoffel.org>,
dannyshih <dannyshih@synology.com>,
axboe@kernel.dk, agk@redhat.com, snitzer@redhat.com,
dm-devel@redhat.com, song@kernel.org,
linux-block@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/4] block: introduce submit_bio_noacct_add_head
Date: Wed, 30 Dec 2020 11:53:22 -0500 [thread overview]
Message-ID: <24556.45186.659863.688675@quad.stoffel.home> (raw)
In-Reply-To: <d841085f-5fd7-bd5c-a40b-fbb953c80598@youngman.org.uk>
>>>>> "antlists" == antlists <antlists@youngman.org.uk> writes:
antlists> On 30/12/2020 00:00, John Stoffel wrote:
dannyshih> From: Danny Shih<dannyshih@synology.com>
dannyshih> Porvide a way for stacking block device to re-submit the bio
dannyshih> which sholud be handled firstly.
>>
>> You're spelling needs to be fixed in these messages.
antlists> ^^^^^^
antlists> It is traditional, when correcting someone else's spelling,
antlists> to make one of your own ... :-)
LOL! Yes, touche! I'm completely abashed.
antlists> Sorry, but if we're being pedantic for furriners, it behoves
antlists> us to be correct ourselves :-)
It does for sure, thanks for the nudge.
next prev parent reply other threads:[~2020-12-30 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 9:18 [PATCH 0/4] Fix order when split bio and send remaining back to itself dannyshih
2020-12-29 9:18 ` [PATCH 1/4] block: introduce submit_bio_noacct_add_head dannyshih
2020-12-30 0:00 ` John Stoffel
2020-12-30 9:51 ` Danny Shih
2020-12-30 17:06 ` John Stoffel
2020-12-30 17:53 ` antlists
2020-12-30 11:35 ` antlists
2020-12-30 16:53 ` John Stoffel [this message]
2020-12-29 9:18 ` [PATCH 2/4] block: use submit_bio_noacct_add_head for split bio sending back dannyshih
2020-12-29 9:18 ` [PATCH 3/4] dm: " dannyshih
2020-12-29 9:18 ` [PATCH 4/4] md: " dannyshih
2020-12-30 23:34 ` [PATCH 0/4] Fix order when split bio and send remaining back to itself Mike Snitzer
2020-12-31 8:28 ` Danny Shih
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=24556.45186.659863.688675@quad.stoffel.home \
--to=john@stoffel.org \
--cc=agk@redhat.com \
--cc=antlists@youngman.org.uk \
--cc=axboe@kernel.dk \
--cc=dannyshih@synology.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).