Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Song Liu <songliubraving@meta.com>,
	linux-raid <linux-raid@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>, David Jeffery <djeffery@redhat.com>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	Xueshi Hu <xueshi.hu@smartx.com>
Subject: Re: [GIT PULL] md-next 20230817
Date: Fri, 18 Aug 2023 09:30:33 -0600	[thread overview]
Message-ID: <9766d333-d233-48c3-9b6b-e511d7a094d4@kernel.dk> (raw)
In-Reply-To: <F71A83B2-C4A5-4168-915C-546CF34CFF34@fb.com>

On 8/17/23 10:51 PM, Song Liu wrote:
> Hi Jens,
> 
> Please consider pulling the following changes for md-next on top of your
> for-6.6/block branch. The major changes are:
> 
> 1. Fix perf regression for raid0 large sequential writes, by Jan Kara;
> 2. Fix split bio iostat for raid0, by David Jeffery;
> 3. Various raid1 fixes, by Heinz Mauelshagen and Xueshi Hu. 

Pulled, thanks.

-- 
Jens Axboe


      reply	other threads:[~2023-08-18 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  4:51 [GIT PULL] md-next 20230817 Song Liu
2023-08-18 15:30 ` 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=9766d333-d233-48c3-9b6b-e511d7a094d4@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=djeffery@redhat.com \
    --cc=heinzm@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-raid@vger.kernel.org \
    --cc=songliubraving@meta.com \
    --cc=xueshi.hu@smartx.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