linux-kernel - Re: [PATCH linux-next v3] mm, page_pool: introduce a new page type for page pool in page type

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] [day] [month] [year] [list]

Message-ID: <8aa31e69-588e-4c7c-9857-553c2d6a2e11@redhat.com>
Date: Mon, 4 Aug 2025 09:38:42 +0200
From: David Hildenbrand <david@...hat.com>
To: Byungchul Park <byungchul@...com>, Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-mm@...ck.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 kernel_team@...ynix.com, harry.yoo@...cle.com, ast@...nel.org,
 daniel@...earbox.net, davem@...emloft.net, kuba@...nel.org, hawk@...nel.org,
 john.fastabend@...il.com, sdf@...ichev.me, saeedm@...dia.com,
 leon@...nel.org, tariqt@...dia.com, mbloch@...dia.com,
 andrew+netdev@...n.ch, edumazet@...gle.com, pabeni@...hat.com,
 akpm@...ux-foundation.org, lorenzo.stoakes@...cle.com,
 Liam.Howlett@...cle.com, vbabka@...e.cz, rppt@...nel.org, surenb@...gle.com,
 mhocko@...e.com, horms@...nel.org, jackmanb@...gle.com, hannes@...xchg.org,
 ziy@...dia.com, ilias.apalodimas@...aro.org, willy@...radead.org,
 brauner@...nel.org, kas@...nel.org, yuzhao@...gle.com,
 usamaarif642@...il.com, baolin.wang@...ux.alibaba.com,
 almasrymina@...gle.com, toke@...hat.com, asml.silence@...il.com,
 bpf@...r.kernel.org, linux-rdma@...r.kernel.org
Subject: Re: [PATCH linux-next v3] mm, page_pool: introduce a new page type
 for page pool in page type

On 04.08.25 03:17, Byungchul Park wrote:
> On Sat, Aug 02, 2025 at 03:07:46PM +1000, Stephen Rothwell wrote:
>> Hi,
>>
>> On Tue, 29 Jul 2025 20:02:10 +0900 Byungchul Park <byungchul@...com> wrote:
>>>
>>> Changes from v2:
>>> 	1. Rebase on linux-next as of Jul 29.
>>
>> Why are you basing development work in linux-next.  That is a
>> constantly rebasing tree.  Please base your work on some stable tree.
> 
> Sorry about the confusing.  I misunderstood how to work for patches
> based on linux-next.
> 
> However, basing on linux-next is still required for this work since more
> than one subsystem is involved, and asked by David Hildenbrand:
> 
>     https://lore.kernel.org/all/20250728105701.GA21732@system.software.com/
> 
> I will base on linux-next and work aiming at either network or mm tree.

I think this is the key part: there is nothing wrong on temporarily 
basing your stuff on linux-next, while we are waiting for this merge 
window to end and relevant patches showing up in either tree after the 
rebase.

You should mention below the "---" your intentions like "This patch is 
supposed to go via the XXX tree, but it currently also depends on 
patches in the YYY tree. For now, this patch is based on linux-next, but 
will apply cleanly (or get rebased) after XXX was rebased."

Also, probably best to indicate the patch as being RFC (instead of 
linux-next) until there is a stable "base".

-- 
Cheers,

David / dhildenb