From: Jens Axboe <axboe@kernel.dk>
To: Song Liu <songliubraving@meta.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [GIT PULL] md-fixes 20230315
Date: Wed, 15 Mar 2023 12:18:54 -0600 [thread overview]
Message-ID: <80411e8d-3cc3-a0a0-1642-c1db5ef96581@kernel.dk> (raw)
In-Reply-To: <07E84E9F-BB2E-4800-99A0-0187460A0669@fb.com>
On 3/15/23 12:14?PM, Song Liu wrote:
>
>
>> On Mar 15, 2023, at 11:09 AM, Jens Axboe <axboe@kernel.dk> wrote:
>>
>> On 3/15/23 12:04?PM, Song Liu wrote:
>>> Hi Jens,
>>>
>>> Please consider pulling the following fixes on top of your for-6.3/block
>>> branch. This set contains two fixes for old issues (by Neil) and one fix
>>> for 6.3 (by Xiao).
>>>
>>> Thanks,
>>> Song
>>>
>>>
>>> The following changes since commit 49d24398327e32265eccdeec4baeb5a6a609c0bd:
>>>
>>> blk-mq: enforce op-specific segment limits in blk_insert_cloned_request (2023-03-02 21:00:20 -0700)
>>>
>>> are available in the Git repository at:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-fixes
>>>
>>> for you to fetch changes up to f6bb5176318186880ff2f16ad65f519b70f04686:
>>>
>>> Subject: md: select BLOCK_LEGACY_AUTOLOAD (2023-03-13 13:34:29 -0700)
>>>
>>> ----------------------------------------------------------------
>>> NeilBrown (2):
>>> md: avoid signed overflow in slot_store()
>>> Subject: md: select BLOCK_LEGACY_AUTOLOAD
>>
>> This one looks like it got botched when applying?
>
> Yeah, I messed up the subject. Thanks for catching it. I just fixed the
> subject. Please pull the following instead.
Pulled.
--
Jens Axboe
prev parent reply other threads:[~2023-03-15 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 18:04 [GIT PULL] md-fixes 20230315 Song Liu
2023-03-15 18:09 ` Jens Axboe
2023-03-15 18:14 ` Song Liu
2023-03-15 18:18 ` 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=80411e8d-3cc3-a0a0-1642-c1db5ef96581@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-raid@vger.kernel.org \
--cc=songliubraving@meta.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