From: Song Liu <song@kernel.org>
To: Xiao Ni <xni@redhat.com>
Cc: Song Liu <songliubraving@fb.com>,
linux-raid <linux-raid@vger.kernel.org>,
Matthew Ruffell <matthew.ruffell@canonical.com>,
Coly Li <colyli@suse.de>,
Guoqing Jiang <guoqing.jiang@cloud.ionos.com>,
Nigel Croxon <ncroxon@redhat.com>,
hch@infradead.org
Subject: Re: [PATCH V2 0/5] md/raid10: Improve handling raid10 discard request
Date: Thu, 4 Feb 2021 09:29:13 -0800 [thread overview]
Message-ID: <CAPhsuW67-Zd7N14DsE+04H1YfBW1rJrfArZypG88mwZT45_+Hg@mail.gmail.com> (raw)
In-Reply-To: <3b95c7ad-f400-0a60-7f7a-6bc3e49967f8@redhat.com>
On Thu, Feb 4, 2021 at 12:39 AM Xiao Ni <xni@redhat.com> wrote:
>
>
>
> On 02/04/2021 04:12 PM, Song Liu wrote:
> > On Wed, Feb 3, 2021 at 11:42 PM Xiao Ni <xni@redhat.com> wrote:
> >> Hi Song
> >>
> >> Please ignore the v2 version. There is a place that needs to be fix.
> >> I'll re-send
> >> v2 version again.
> > What did you change in the new v2? Removing "extern" in the header?
> > For small changes like this, I can just update it while applying the patches.
> > If we do need resend (for bigger changes), it's better to call it v3.
>
> Yes, it only removes "extern" in patch1.
> >
> > I was testing the first v2 in the past hour or so, it looks good in the test.
> > I will take a closer look tomorrow. On the other hand, we are getting close
> > to the 5.12 merge window, so it is a little too late for bigger
> > changes like this.
> > Therefore, I would prefer to wait until 5.13. If you need it in 5.12 for some
> > reason, please let me know.
> Is md-next a branch that is used before merging? If so, could you merge
> the patches
> to md-next if your test pass? There is a bug that needs to be fixed in
> rhel. We can
> backport the patches if you merge the patches to md-next.
Yes, I can apply them to md-next. But I rebase it from time to time, so the
hash tag will change.
Thanks,
Song
next prev parent reply other threads:[~2021-02-04 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 5:57 [PATCH V2 0/5] md/raid10: Improve handling raid10 discard request Xiao Ni
2021-02-04 5:57 ` [PATCH V2 1/5] md: add md_submit_discard_bio() for submitting discard bio Xiao Ni
2021-02-04 5:57 ` [PATCH V2 2/5] md/raid10: extend r10bio devs to raid disks Xiao Ni
2021-02-04 5:57 ` [PATCH V2 3/5] md/raid10: pull the code that wait for blocked dev into one function Xiao Ni
2021-02-04 5:57 ` [PATCH V2 4/5] md/raid10: improve raid10 discard request Xiao Ni
2021-02-04 5:57 ` [PATCH V2 5/5] md/raid10: improve discard request for far layout Xiao Ni
2021-02-04 7:38 ` [PATCH V2 0/5] md/raid10: Improve handling raid10 discard request Xiao Ni
2021-02-04 8:12 ` Song Liu
2021-02-04 8:39 ` Xiao Ni
2021-02-04 17:29 ` Song Liu [this message]
2021-02-04 7:50 Xiao Ni
2021-02-15 4:05 ` Matthew Ruffell
2021-02-20 8:12 ` Xiao Ni
2021-02-24 8:41 ` Song Liu
2021-03-11 3:55 Adrian Huang12
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=CAPhsuW67-Zd7N14DsE+04H1YfBW1rJrfArZypG88mwZT45_+Hg@mail.gmail.com \
--to=song@kernel.org \
--cc=colyli@suse.de \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=hch@infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=matthew.ruffell@canonical.com \
--cc=ncroxon@redhat.com \
--cc=songliubraving@fb.com \
--cc=xni@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 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).