From: Jens Axboe <axboe@kernel.dk>
To: Song Liu <songliubraving@fb.com>,
linux-raid <linux-raid@vger.kernel.org>
Cc: Zhao Heming <heming.zhao@suse.com>,
Pankaj Gupta <pankaj.gupta@cloud.ionos.com>,
Kevin Vigor <kvigor@gmail.com>,
"Dae R. Jeong" <dae.r.jeong@kaist.ac.kr>
Subject: Re: [GIT PULL] md-next 20201130
Date: Mon, 30 Nov 2020 15:53:16 -0700 [thread overview]
Message-ID: <5719b897-a662-db59-16f2-d21ae2e5a83f@kernel.dk> (raw)
In-Reply-To: <84FD2F29-B2F8-4026-A93D-5E28F28A3B4B@fb.com>
On 11/30/20 11:15 AM, Song Liu wrote:
> Summary:
> 1. Fix race condition in md_ioctl(), by Dae R. Jeong;
> 2. Initialize read_slot properly for raid10, by Kevin Vigor;
> 3. Code cleanup, by Pankaj Gupta;
> 4. md-cluster resync/reshape fix, by Zhao Heming.
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-11-30 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 18:15 [GIT PULL] md-next 20201130 Song Liu
2020-11-30 22:53 ` Jens Axboe [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=5719b897-a662-db59-16f2-d21ae2e5a83f@kernel.dk \
--to=axboe@kernel.dk \
--cc=dae.r.jeong@kaist.ac.kr \
--cc=heming.zhao@suse.com \
--cc=kvigor@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=pankaj.gupta@cloud.ionos.com \
--cc=songliubraving@fb.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).