Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 21 Apr 2023 20:24:58 +0100
From:   Conor Dooley <conor@kernel.org>
To:     Konstantin Ryabitsev <konstantin.ryabitsev@linux.dev>
Cc:     Palmer Dabbelt <palmer@dabbelt.com>, alexghiti@rivosinc.com,
        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
Message-ID: <20230421-uneaten-obvious-250d95c86560@spud>
References: <mhng-bb70f74f-2b5b-4880-b7bf-975e67dc554e@palmer-ri-x1c9>
 <ba235aa677a561ceb2dc776414403dc0@linux.dev>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="cYLCWmWMPROB1qtr"
Content-Disposition: inline
In-Reply-To: <ba235aa677a561ceb2dc776414403dc0@linux.dev>
Precedence: bulk


--cYLCWmWMPROB1qtr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 21, 2023 at 07:10:14PM +0000, Konstantin Ryabitsev wrote:
> 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=3D73360=
3)
> >> base-commit-tag: v6.3-rc1
> >=20
> > 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.
>=20
> 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!

--cYLCWmWMPROB1qtr
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZELjCgAKCRB4tDGHoIJi
0s1yAP9XTAhQrJD/xmNk2JTUsPIU6e0uJxU1rNaDElF8T2ioggD/RuvGZYpDeAT8
rVM1QBn5DNrHVZWw5EILFxMXOgo1hA4=
=0mnA
-----END PGP SIGNATURE-----

--cYLCWmWMPROB1qtr--