Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230815091931.4dd2b277@canb.auug.org.au> <8c946512-0cc4-fbc5-ca36-0e2c6d636eb2@huaweicloud.com>
 <c39a3bff-01b9-4007-80ac-00ce2b11a902@kernel.dk>
In-Reply-To: <c39a3bff-01b9-4007-80ac-00ce2b11a902@kernel.dk>
From:   Song Liu <song@kernel.org>
Date:   Tue, 15 Aug 2023 23:58:45 +0800
Message-ID: <CAPhsuW7ck4Bb8NVUdgZZJqzNCYMgT9rspKshr2Zi=8xo2cQLaw@mail.gmail.com>
Subject: Re: linux-next: Fixes tag needs some work in the block tree
To:     Jens Axboe <axboe@kernel.dk>
Cc:     Yu Kuai <yukuai1@huaweicloud.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        "yukuai (C)" <yukuai3@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Aug 15, 2023 at 11:08=E2=80=AFPM Jens Axboe <axboe@kernel.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_t=
akeover()")
> >>
> >> 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