From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "Palmer Dabbelt" <palmer@dabbelt.com>, alexghiti@rivosinc.com
Cc: aou@eecs.berkeley.edu, linux-kbuild@vger.kernel.org,
ndesaulniers@google.com, linux-kernel@vger.kernel.org,
bjorn@kernel.org, npiggin@gmail.com,
"Paul Walmsley" <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v9 0/6] Introduce 64b relocatable kernel
Date: Fri, 21 Apr 2023 19:10:14 +0000 [thread overview]
Message-ID: <ba235aa677a561ceb2dc776414403dc0@linux.dev> (raw)
In-Reply-To: <mhng-bb70f74f-2b5b-4880-b7bf-975e67dc554e@palmer-ri-x1c9>
April 21, 2023 2:59 PM, "Palmer Dabbelt" <palmer@dabbelt.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
WARNING: multiple messages have this Message-ID (diff)
From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "Palmer Dabbelt" <palmer@dabbelt.com>, alexghiti@rivosinc.com
Cc: aou@eecs.berkeley.edu, linux-kbuild@vger.kernel.org,
ndesaulniers@google.com, linux-kernel@vger.kernel.org,
bjorn@kernel.org, npiggin@gmail.com,
"Paul Walmsley" <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v9 0/6] Introduce 64b relocatable kernel
Date: Fri, 21 Apr 2023 19:10:14 +0000 [thread overview]
Message-ID: <ba235aa677a561ceb2dc776414403dc0@linux.dev> (raw)
In-Reply-To: <mhng-bb70f74f-2b5b-4880-b7bf-975e67dc554e@palmer-ri-x1c9>
April 21, 2023 2:59 PM, "Palmer Dabbelt" <palmer@dabbelt.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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "Palmer Dabbelt" <palmer@dabbelt.com>, alexghiti@rivosinc.com
Cc: aou@eecs.berkeley.edu, linux-kbuild@vger.kernel.org,
ndesaulniers@google.com, linux-kernel@vger.kernel.org,
npiggin@gmail.com, bjorn@kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v9 0/6] Introduce 64b relocatable kernel
Date: Fri, 21 Apr 2023 19:10:14 +0000 [thread overview]
Message-ID: <ba235aa677a561ceb2dc776414403dc0@linux.dev> (raw)
In-Reply-To: <mhng-bb70f74f-2b5b-4880-b7bf-975e67dc554e@palmer-ri-x1c9>
April 21, 2023 2:59 PM, "Palmer Dabbelt" <palmer@dabbelt.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
next prev parent reply other threads:[~2023-04-21 19:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 4:53 [PATCH v9 0/6] Introduce 64b relocatable kernel Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 1/6] riscv: Prepare EFI header for relocatable kernels Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 2/6] riscv: Move .rela.dyn outside of init to avoid empty relocations Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 3/6] riscv: Introduce CONFIG_RELOCATABLE Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 4/6] powerpc: Move script to check relocations at compile time in scripts/ Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 5/6] riscv: Check relocations at compile time Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 6/6] riscv: Use --emit-relocs in order to move .rela.dyn in init Alexandre Ghiti
2023-03-29 4:53 ` Alexandre Ghiti
2023-09-12 23:34 ` Fangrui Song
2023-09-12 23:34 ` Fangrui Song
2023-04-19 14:56 ` [PATCH v9 0/6] Introduce 64b relocatable kernel Palmer Dabbelt
2023-04-19 14:56 ` Palmer Dabbelt
2023-04-20 17:40 ` patchwork-bot+linux-riscv
2023-04-20 17:40 ` patchwork-bot+linux-riscv
2023-04-20 17:40 ` patchwork-bot+linux-riscv
2023-04-21 18:59 ` Palmer Dabbelt
2023-04-21 18:59 ` Palmer Dabbelt
2023-04-21 18:59 ` Palmer Dabbelt
2023-04-21 19:10 ` Konstantin Ryabitsev [this message]
2023-04-21 19:10 ` Konstantin Ryabitsev
2023-04-21 19:10 ` Konstantin Ryabitsev
2023-04-21 19:24 ` Conor Dooley
2023-04-21 19:24 ` Conor Dooley
2023-04-21 19:24 ` Conor Dooley
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=ba235aa677a561ceb2dc776414403dc0@linux.dev \
--to=konstantin.ryabitsev@linux.dev \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.