linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Blomdell <anders.blomdell@gmail.com>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: dchinner@redhat.com, djwong@kernel.org, hch@lst.de,
	kjell.m.randa@gmail.com, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org, willy@infradead.org,
	wozizhi@huawei.com
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to a24cae8fc1f1
Date: Wed, 28 Aug 2024 14:15:58 +0200	[thread overview]
Message-ID: <9e95498c-3924-4865-9012-ba92c4f4cf48@gmail.com> (raw)
In-Reply-To: <878qwhl2l5.fsf@debian-BULLSEYE-live-builder-AMD64>

Dave,

Do you mind if I CC the path to stable@vger.kernel.org (and maybe GKH)?

/Anders

On 2024-08-28 05:54, Chandan Babu R wrote:
> On Tue, Aug 27, 2024 at 05:24:36 PM +0200, Anders Blomdell wrote:
>> Since 6.10 is still marked as a stable release, maybe this shold go into 6.10-fixes branch as well?
>>
>>    Dave Chinner (1):
>>        [95179935bead] xfs: xfs_finobt_count_blocks() walks the wrong btree
>>
> 
> xfs-linux git repository's xfs-6.10-fixes is not meant for collecting patches
> for stable kernels.
> 
> Also, the patch mentioned above cannot be merged into 6.10.y for the following
> reasons:
> 1. The 6.11 kernel has not been released yet.
> 2. No developer has signed up for backporting patches to 6.10.y.
> 

  reply	other threads:[~2024-08-28 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 15:05 [ANNOUNCE] xfs-linux: for-next updated to a24cae8fc1f1 Chandan Babu R
2024-08-27 15:24 ` Anders Blomdell
2024-08-28  3:54   ` Chandan Babu R
2024-08-28 12:15     ` Anders Blomdell [this message]
2024-08-29  0:04       ` Dave Chinner

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=9e95498c-3924-4865-9012-ba92c4f4cf48@gmail.com \
    --to=anders.blomdell@gmail.com \
    --cc=chandanbabu@kernel.org \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=kjell.m.randa@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=wozizhi@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).