Linux RAID subsystem development
 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.13 0/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer
Date: Mon, 27 Jan 2025 13:45:15 +0100	[thread overview]
Message-ID: <2025012755-dimmed-dismount-a5a5@gregkh> (raw)
In-Reply-To: <2025012752-jolly-chowtime-d498@gregkh>

On Mon, Jan 27, 2025 at 10:11:30AM +0100, Greg KH wrote:
> On Mon, Jan 27, 2025 at 04:49:23PM +0800, Yu Kuai wrote:
> > 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 5.
> 
> Why were these all not properly taggeed for stable inclusion to start
> with?

Also, as these are not in a released kernel just yet, why should we
include them in one now before 6.14-rc1 is out?

thanks,

greg k-h

  reply	other threads:[~2025-01-27 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27  8:49 [PATCH 6.13 0/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27  8:49 ` [PATCH 6.13 1/5] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write() Yu Kuai
2025-01-27  8:49 ` [PATCH 6.13 2/5] md/md-bitmap: remove the last parameter for bimtap_ops->endwrite() Yu Kuai
2025-01-27  8:49 ` [PATCH 6.13 3/5] md: add a new callback pers->bitmap_sector() Yu Kuai
2025-01-27  8:49 ` [PATCH 6.13 4/5] md/raid5: implement pers->bitmap_sector() Yu Kuai
2025-01-27  8:49 ` [PATCH 6.13 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27  9:11 ` [PATCH 6.13 0/5] " Greg KH
2025-01-27 12:45   ` Greg KH [this message]
2025-02-06  1:46     ` 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=2025012755-dimmed-dismount-a5a5@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