[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48f834c2-b283-4b02-9407-4a0842d4ed72@kernel.dk>
Date: Tue, 15 Aug 2023 10:07:45 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Song Liu <song@...nel.org>
Cc: Yu Kuai <yukuai1@...weicloud.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: linux-next: Fixes tag needs some work in the block tree
On 8/15/23 9:58 AM, Song Liu wrote:
> On Tue, Aug 15, 2023 at 11:08?PM Jens Axboe <axboe@...nel.dk> wrote:
>>
>> On 8/14/23 9:21 PM, Yu Kuai wrote:
>>> Hi,
>>>
>>> ? 2023/08/15 7:19, Stephen Rothwell ??:
>>>> Hi all,
>>>>
>>>> In commit
>>>>
>>>> 71070e7bd25d ("md/raid10: fix a 'conf->barrier' leakage in raid10_takeover()")
>>>>
>>>> Fixes tag
>>>>
>>>> Fixes: 4d27e927344a ("md: don't quiesce in mddev_suspend()")
>>>>
>>>> has these problem(s):
>>>>
>>>> - Target SHA1 does not exist
>>>
>>> Sorry about this, the commit was picked from previous md-next branch,
>>> and I didn't know that it will change...
>>
>> It's most likely not your fault, I'm guessing Song rebased that branch
>> and this is why the sha changed. Song?
>
> Yeah, it is my fault. I am really sorry for this issue.
>
>>
>>> Is there any way that I can fix this ?
>>
>> Only way to fix this is if I rewind my branch and Song updates his
>> branch to not have this issue, and then sends a new pull request.
>
> Yes please. Let's fix this.
Please send a new one, I've dropped the old one.
--
Jens Axboe
Powered by blists - more mailing lists