From: Stephen Rothwell <sfr@canb•auug.org.au>
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, willy@infradead•org,
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: Tue, 9 Jul 2024 08:40:23 +1000 [thread overview]
Message-ID: <20240709084023.585109fe@canb.auug.org.au> (raw)
In-Reply-To: <Zoxkap1DtwZ-1tjI@bombadil.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Hi Luis,
On Mon, 8 Jul 2024 15:12:58 -0700 Luis Chamberlain <mcgrof@kernel•org> 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?
Yes :-)
The rules for linux-next look like this:
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
We don't want code that is not going into the next merge window
creating conflicts and possible run time problems wasting time for
people who are trying to stabilise code that is destined for the next
merge window.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-07-08 22:40 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
2024-07-08 22:40 ` Stephen Rothwell [this message]
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=20240709084023.585109fe@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=brauner@kernel$(echo .)org \
--cc=chandan.babu@oracle$(echo .)com \
--cc=cl@os$(echo .)amperecomputing.com \
--cc=david@fromorbit$(echo .)com \
--cc=djwong@kernel$(echo .)org \
--cc=gost.dev@samsung$(echo .)com \
--cc=hare@suse$(echo .)de \
--cc=hch@lst$(echo .)de \
--cc=john.g.garry@oracle$(echo .)com \
--cc=kernel@pankajraghav$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-xfs@vger$(echo .)kernel.org \
--cc=mcgrof@kernel$(echo .)org \
--cc=p.raghav@samsung$(echo .)com \
--cc=willy@infradead$(echo .)org \
--cc=yang@os$(echo .)amperecomputing.com \
--cc=ziy@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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