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@xxxxxx> 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@xxxxxxxxxxxxxxxxxxx/
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
