On Fri, Apr 21, 2023 at 07:10:14PM +0000, Konstantin Ryabitsev wrote: > April 21, 2023 2:59 PM, "Palmer Dabbelt" <pal...@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.
A patchwork-ism or a patchew-ism? Drew Jones was my source for this, but he had said the thing to do in QEMU-land was put a: Based-on: $message-id in your cover letter for each thing that you depend on. I'm not entirely sure if that meant each series or each patch. I think patchew picks that up and dumps in it on a patchew github account that the CI might pick up on. From the QEMU docs: <quote> It is also okay to base patches on top of other on-going work that is not yet part of the git master branch. To aid continuous integration tools, such as `patchew <http://patchew.org/QEMU/>`__, you should `add a tag <https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg01288.html>`__ line ``Based-on: $MESSAGE_ID`` to your cover letter to make the series dependency obvious. <\quote> FWIW, my vote is for something with a message-id, rather than those patchwork series links that you can't dump into b4!
signature.asc
Description: PGP signature
