public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: stable@vger.kernel.org, song@kernel.org, yukuai3@huawei.com,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH 6.6 0/6] md/md-bitmap: move bitmap_{start, end}write to md upper layer
Date: Tue, 4 Feb 2025 12:40:12 +0100	[thread overview]
Message-ID: <2025020447-hesitant-corroding-16c1@gregkh> (raw)
In-Reply-To: <20250127085351.3198083-1-yukuai1@huaweicloud.com>

On Mon, Jan 27, 2025 at 04:53:45PM +0800, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
> 
> This set fix reported problem:
> 
> https://lore.kernel.org/all/CAJpMwyjmHQLvm6zg1cmQErttNNQPDAAXPKM3xgTjMhbfts986Q@mail.gmail.com/
> https://lore.kernel.org/all/ADF7D720-5764-4AF3-B68E-1845988737AA@flyingcircus.io/
> 
> See details in patch 6.

Please redo this series and describe in it what you changed from the
original commits, as these are not just normal cherry-picks at all.

thanks,

greg k-h

  parent reply	other threads:[~2025-02-04 11:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27  8:53 [PATCH 6.6 0/6] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 1/6] md/raid5: recheck if reshape has finished with device_lock held Yu Kuai
2025-01-27 11:25   ` Sasha Levin
2025-01-27  8:53 ` [PATCH 6.6 2/6] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write() Yu Kuai
2025-02-04 11:38   ` Greg KH
2025-01-27  8:53 ` [PATCH 6.6 3/6] md/md-bitmap: remove the last parameter for bimtap_ops->endwrite() Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 4/6] md: add a new callback pers->bitmap_sector() Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 5/6] md/raid5: implement pers->bitmap_sector() Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 6/6] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-02-04 11:40 ` Greg KH [this message]
2025-02-06  1:53   ` [PATCH 6.6 0/6] " Yu Kuai

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=2025020447-hesitant-corroding-16c1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --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