Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] mkfs: add config file for the 2026 LTS kernel
Date: Mon, 21 Sep 2026 15:45:36 -0700	[thread overview]
Message-ID: <20260921224536.GQ6283@frogsfrogsfrogs> (raw)
In-Reply-To: <arDrUJPMZW7hXC8N@infradead.org>

On Mon, Sep 21, 2026 at 01:31:12AM -0700, Christoph Hellwig wrote:
> On Sun, Sep 20, 2026 at 11:14:43PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > Add a config file for 7.3 since it'll be the LTS.
> 
> I wonder if they are going to move it given that 7.4 should land
> just after new years?  So maybe wait a bit with this, even if it
> does look fine.

I dunno.  From dhansen's PHB predictor:

the v7.3 kernel predictions: merge window closes on Sunday, 2026-08-30 and release on Sunday, 2026-10-25
the v7.4 kernel predictions: merge window closes on Sunday, 2026-11-08 and release on Sunday, 2027-01-03

Either someone should ask gregkh, or we should send a flood of bugfixes
to slow down 7.3. ;)

--D

  reply	other threads:[~2026-09-21 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  6:13 [PATCHSET 2/2] xfsprogs: enable metadir by default Darrick J. Wong
2026-09-21  6:14 ` [PATCH 1/2] mkfs: add config file for the 2026 LTS kernel Darrick J. Wong
2026-09-21  8:31   ` Christoph Hellwig
2026-09-21 22:45     ` Darrick J. Wong [this message]
2026-09-21  6:14 ` [PATCH 2/2] mkfs: enable metadata directory trees by default Darrick J. Wong

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=20260921224536.GQ6283@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    /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