linux-kernel - Re: [PATCH v9 00/10] enable bs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240709084023.585109fe@canb.auug.org.au>
Date: Tue, 9 Jul 2024 08:40:23 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: "Pankaj Raghav (Samsung)" <kernel@...kajraghav.com>, Chandan Babu R
 <chandan.babu@...cle.com>, djwong@...nel.org, david@...morbit.com,
 willy@...radead.org, Christian Brauner <brauner@...nel.org>, Stephen
 Rothwell <sfr@...b.auug.org.au>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, akpm@...ux-foundation.org,
 yang@...amperecomputing.com, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org, john.g.garry@...cle.com, linux-fsdevel@...r.kernel.org,
 hare@...e.de, p.raghav@...sung.com, gost.dev@...sung.com,
 cl@...amperecomputing.com, linux-xfs@...r.kernel.org, hch@....de, Zi Yan
 <ziy@...dia.com>
Subject: Re: [PATCH v9 00/10] enable bs > ps in XFS

Hi Luis,

On Mon, 8 Jul 2024 15:12:58 -0700 Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Thu, Jul 04, 2024 at 11:23:10AM +0000, Pankaj Raghav (Samsung) wrote:
> > From: Pankaj Raghav <p.raghav@...sung.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

Content of type "application/pgp-signature" skipped