[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba235aa677a561ceb2dc776414403dc0@linux.dev>
Date: Fri, 21 Apr 2023 19:10:14 +0000
From: "Konstantin Ryabitsev" <konstantin.ryabitsev@...ux.dev>
To: "Palmer Dabbelt" <palmer@...belt.com>, alexghiti@...osinc.com
Cc: aou@...s.berkeley.edu, linux-kbuild@...r.kernel.org,
ndesaulniers@...gle.com, linux-kernel@...r.kernel.org,
bjorn@...nel.org, npiggin@...il.com,
"Paul Walmsley" <paul.walmsley@...ive.com>,
linux-riscv@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v9 0/6] Introduce 64b relocatable kernel
April 21, 2023 2:59 PM, "Palmer Dabbelt" <palmer@...belt.com> wrote:
>> riscv: Use PUD/P4D/PGD pages for the linear mapping
>> (https://patchwork.kernel.org/project/linux-riscv/list/?series=733603)
>> base-commit-tag: v6.3-rc1
>
> The QEMU CI has some way to say "this depends on an un-merged patch set sent as $MESSAGE_ID", not
> sure if that's a b4-ism but it's a bit less confusing.
I think it's patchwork-ism, actually. B4 will eventually learn to be able to include dependent series info and automatically retrieve/apply them in the proper order on "shazam", but it can't do that yet.
-K
Powered by blists - more mailing lists