From: Matthew Wilcox <willy@infradead.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
Chandan Babu R <chandan.babu@oracle.com>,
djwong@kernel.org, david@fromorbit.com,
Christian Brauner <brauner@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
akpm@linux-foundation.org, yang@os.amperecomputing.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
john.g.garry@oracle.com, linux-fsdevel@vger.kernel.org,
hare@suse.de, p.raghav@samsung.com, gost.dev@samsung.com,
cl@os.amperecomputing.com, linux-xfs@vger.kernel.org, hch@lst.de,
Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH v9 00/10] enable bs > ps in XFS
Date: Mon, 8 Jul 2024 23:27:27 +0100 [thread overview]
Message-ID: <Zoxnz7R5EBb6SCR7@casper.infradead.org> (raw)
In-Reply-To: <Zoxkap1DtwZ-1tjI@bombadil.infradead.org>
On Mon, Jul 08, 2024 at 03:12:58PM -0700, Luis Chamberlain wrote:
> On Thu, Jul 04, 2024 at 11:23:10AM +0000, Pankaj Raghav (Samsung) wrote:
> > From: Pankaj Raghav <p.raghav@samsung.com>
> >
> > This is the ninth version of the series that enables block size > page size
> > (Large Block Size) in XFS.
>
> It's too late to get this in for v6.11, but I'd like to get it more exposure
> for testing. Anyone oppose getting this to start being merged now into
> linux-next so we can start testing for *more* than a kernel release cycle?
That's not how linux-next works. It's only for patches which are
destined for the next merge window, not for the one after that.
next prev parent reply other threads:[~2024-07-08 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240704112320.82104-1-kernel@pankajraghav.com>
2024-07-08 22:12 ` [PATCH v9 00/10] enable bs > ps in XFS Luis Chamberlain
2024-07-08 22:27 ` Matthew Wilcox [this message]
2024-07-08 22:40 ` 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=Zoxnz7R5EBb6SCR7@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=cl@os.amperecomputing.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=kernel@pankajraghav.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=yang@os.amperecomputing.com \
--cc=ziy@nvidia.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