From: Logan Gunthorpe <logang@deltatee.com>
To: Song Liu <songliubraving@fb.com>, Jens Axboe <axboe@kernel.dk>,
linux-raid <linux-raid@vger.kernel.org>
Cc: David Sloan <david.sloan@eideticom.com>,
Yu Kuai <yukuai3@huawei.com>,
Mateusz Grzonka <mateusz.grzonka@intel.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
XU pengfei <xupengfei@nfschina.com>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
Zhou nan <zhounan@nfschina.com>
Subject: Re: [GIT PULL] md-next 20220921
Date: Wed, 21 Sep 2022 16:37:53 -0600 [thread overview]
Message-ID: <b347b8e9-d136-3430-5be0-b4b14d067dc4@deltatee.com> (raw)
In-Reply-To: <9C523D34-6134-4F86-A357-5F306AC3DD07@fb.com>
On 2022-09-21 15:33, Song Liu wrote:
> Hi Jens,
>
> Please consider pulling the following changes for md-next on top of your
> for-6.1/block branch (for-6.1/drivers branch doesn't exist yet).
>
> The major changes are:
>
> 1. Various raid5 fix and clean up, by Logan Gunthorpe and David Sloan.
> 2. Raid10 performance optimization, by Yu Kuai.
> 3. Generate CHANGE uevents for md device, by Mateusz Grzonka.
I may have hit a bug with my tests on the latest md-next branch. Still
trying to hit it again. The last tests I ran for several days with some
patches on the previous md-next branch, but I didn't have Mateusz's
changes, and it also looks like the branch was rebased today so it could
be caused by either of those things. I'll let you know when I know more.
Logan
next prev parent reply other threads:[~2022-09-21 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 21:33 [GIT PULL] md-next 20220921 Song Liu
2022-09-21 22:37 ` Logan Gunthorpe [this message]
2022-09-21 23:44 ` Logan Gunthorpe
2022-09-22 0:40 ` Song Liu
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=b347b8e9-d136-3430-5be0-b4b14d067dc4@deltatee.com \
--to=logang@deltatee.com \
--cc=axboe@kernel.dk \
--cc=david.sloan@eideticom.com \
--cc=guoqing.jiang@linux.dev \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz.grzonka@intel.com \
--cc=songliubraving@fb.com \
--cc=ssengar@linux.microsoft.com \
--cc=xupengfei@nfschina.com \
--cc=yukuai3@huawei.com \
--cc=zhounan@nfschina.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