[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPhsuW7ck4Bb8NVUdgZZJqzNCYMgT9rspKshr2Zi=8xo2cQLaw@mail.gmail.com>
Date: Tue, 15 Aug 2023 23:58:45 +0800
From: Song Liu <song@...nel.org>
To: Jens Axboe <axboe@...nel.dk>
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 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.
Song
Powered by blists - more mailing lists