linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <song@kernel.org>
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>
Subject: Re: linux-next: Fixes tag needs some work in the block tree
Date: Wed, 16 Aug 2023 00:26:25 +0800	[thread overview]
Message-ID: <CAPhsuW5AHQkf6wO_4Z6VFbTCxNN9GchW_ZPxmC1vtc23ByPc6g@mail.gmail.com> (raw)
In-Reply-To: <a30e4e08-7b8c-498c-b8af-82262b3ec6ff@kernel.dk>

On Wed, Aug 16, 2023 at 12:20 AM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 8/15/23 10:17 AM, Song Liu wrote:
> > On Wed, Aug 16, 2023 at 12:07?AM Jens Axboe <axboe@kernel.dk> wrote:
> >>
> >> On 8/15/23 9:58 AM, Song Liu wrote:
> >>> On Tue, Aug 15, 2023 at 11:08?PM 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_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.
> >
> > Is this the for-6.6/block branch? I haven't seen the change yet. The top
> > commit on the branch (as I see) is
> >
> > 306d74055754 ("ublk: Switch to memdup_user_nul() helper")
>
> Where are you looking? It's at:

I am looking at

https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git

It appears to be some lag from git server?

Thanks,
Song

>
> commit 66a6a5d0ec852eaced589da066376e69397cd71e (origin/for-6.6/block, for-6.6/block)
> Author: Ruan Jinjie <ruanjinjie@huawei.com>
> Date:   Tue Aug 15 19:48:14 2023 +0800
>
>     ublk: Switch to memdup_user_nul() helper
>
> since about 15 min ago.

  reply	other threads:[~2023-08-15 16:27 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 23:19 linux-next: Fixes tag needs some work in the block tree Stephen Rothwell
2023-08-15  3:21 ` Yu Kuai
2023-08-15 15:08   ` Jens Axboe
2023-08-15 15:58     ` Song Liu
2023-08-15 16:07       ` Jens Axboe
2023-08-15 16:17         ` Song Liu
2023-08-15 16:20           ` Jens Axboe
2023-08-15 16:26             ` Song Liu [this message]
2023-08-15 16:31               ` Jens Axboe
2023-08-15 16:51                 ` Song Liu
2023-08-15 16:59                   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2023-11-22 21:51 Stephen Rothwell
2023-06-18 22:22 Stephen Rothwell
2023-06-20  5:41 ` Chaitanya Kulkarni
2023-06-13 22:33 Stephen Rothwell
2023-03-20 21:28 Stephen Rothwell
2023-03-20 21:30 ` Jens Axboe
2022-11-28 21:27 Stephen Rothwell
2022-11-28 23:39 ` Damien Le Moal
2022-11-29  2:30   ` Jens Axboe
2022-11-29  2:50     ` Damien Le Moal
2022-07-27 22:06 Stephen Rothwell
2022-06-22 23:21 Stephen Rothwell
2022-06-22 23:44 ` Jens Axboe
2022-06-23  8:11   ` Dylan Yudaken
2022-04-28  1:44 Stephen Rothwell
2022-03-28 21:02 Stephen Rothwell
2022-03-22 20:49 Stephen Rothwell
2022-03-23  1:45 ` Jens Axboe
2022-01-03 21:25 Stephen Rothwell
2021-10-19 21:46 Stephen Rothwell
2021-08-22  3:24 Stephen Rothwell
2021-05-18 22:01 Stephen Rothwell
2021-05-19 19:25 ` Sergey Shtylyov
2021-05-19 21:55   ` Jens Axboe
2021-05-05 22:23 Stephen Rothwell
2021-05-09  1:49 ` Minwoo Im
2021-03-04 23:52 Stephen Rothwell
2021-03-05  0:26 ` Jens Axboe
2021-03-05  7:46   ` Christoph Hellwig
2021-03-05 15:53     ` Jens Axboe
2021-02-22 21:01 Stephen Rothwell
2021-02-22 21:15 ` Chaitanya Kulkarni
2021-02-20  4:51 Stephen Rothwell
2021-02-20  4:57 ` Jens Axboe
2021-02-04 20:13 Stephen Rothwell
2021-01-25  9:40 Stephen Rothwell
2021-01-25 18:35 ` Paolo Valente
2021-01-25 18:39   ` Jens Axboe
2021-01-26 13:29     ` Jan Kara
2021-01-26 15:47       ` Jens Axboe
2021-01-26 16:01         ` Jan Kara
2021-01-26 16:05           ` Jens Axboe
2020-12-17 20:38 Stephen Rothwell
2020-12-17 20:42 ` Jens Axboe
2020-12-01 21:02 Stephen Rothwell
2020-12-01 21:09 ` Jens Axboe
2020-12-01 21:44   ` Stephen Rothwell
2020-12-01 21:52     ` Jens Axboe
2020-11-30 21:28 Stephen Rothwell
2020-09-24 22:38 Stephen Rothwell
2020-07-29 22:08 Stephen Rothwell
2020-07-29 22:12 ` Stephen Rothwell
2020-07-30 15:04   ` Jens Axboe
2020-06-28 22:05 Stephen Rothwell
2020-06-29 16:21 ` Pavel Begunkov
2020-06-29 16:25   ` Jens Axboe
2020-06-29 22:36     ` Stephen Rothwell
2020-06-29 22:45       ` Jens Axboe
2020-06-26 23:07 Stephen Rothwell
2020-06-27  1:32 ` Jens Axboe
2020-06-27  1:56   ` Konstantin Ryabitsev
2020-06-27  2:25     ` Jens Axboe
2020-06-27  5:12       ` Stephen Rothwell
2020-06-28 13:38         ` Jens Axboe
2020-06-27  5:01     ` Stephen Rothwell
2020-06-27 11:18       ` Pavel Begunkov
2020-05-28 21:10 Stephen Rothwell
2020-03-22 14:08 Stephen Rothwell
2019-10-24  6:16 Stephen Rothwell
2019-10-07 20:16 Stephen Rothwell
2019-10-10 17:36 ` Bart Van Assche
2019-10-11  0:42   ` Stephen Rothwell
2019-09-10 14:57 Stephen Rothwell
2019-07-11 21:35 Stephen Rothwell
2019-07-11 22:03 ` Jens Axboe
2019-07-12  8:47   ` Minwoo Im
2019-02-21 20:39 Stephen Rothwell

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=CAPhsuW5AHQkf6wO_4Z6VFbTCxNN9GchW_ZPxmC1vtc23ByPc6g@mail.gmail.com \
    --to=song@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).