From: Mark Brown <broonie@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
linux-doc@vger.kernel.org, workflows@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] docs: submitting-patches: Require base tree information
Date: Mon, 26 Oct 2026 20:51:35 +0000 [thread overview]
Message-ID: <at-9VwE3BL_3OXNP@sirena.org.uk> (raw)
In-Reply-To: <20261026201905.GC2005298@killaraus.ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Mon, Oct 26, 2026 at 10:19:05PM +0200, Laurent Pinchart wrote:
> On Mon, Oct 26, 2026 at 04:37:28PM +0100, Geert Uytterhoeven wrote:
> > On Mon, 26 Oct 2026 at 15:53, Laurent Pinchart wrote:
> > > Hence the prerequisite-patch-id and base tree information. Or do you
> > > mean your base is not public at all, neither in the form of a branch
> > > pushed to a public tree, nor as prerequisite patches sent to a public
> > > list ?
> > Correct.
> How am I supposed to review or apply something that depends on work that
> is not public ?
It depends a lot on what the base commit is doing, if it's directly
relevant to the patch it's an issue but if it's unrelated work for
platform enablement that's needed for testing the changes then it
isn't so relevant. This isn't insurmountable, you can cherry pick the
changes over to a clean branch or something, but there's new failure
modes introduced by being explicit about the commit (the number of times
I've had to unwind a series apply in b4 because it paid attention to an
unsuitable sender specified base...).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-26 20:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 21:22 Eric Biggers
2026-10-20 22:07 ` Konstantin Ryabitsev
2026-10-21 6:07 ` Randy Dunlap
2026-10-21 6:35 ` Krzysztof Kozlowski
2026-10-21 6:44 ` Eric Biggers
2026-10-21 6:47 ` Krzysztof Kozlowski
2026-10-21 3:17 ` Weijie Yuan
2026-10-21 6:26 ` Krzysztof Kozlowski
2026-10-21 6:39 ` Eric Biggers
2026-10-21 6:41 ` Krzysztof Kozlowski
2026-10-21 6:49 ` Eric Biggers
2026-10-21 11:55 ` Krzysztof Kozlowski
2026-10-21 15:04 ` Konstantin Ryabitsev
2026-10-21 15:49 ` Krzysztof Kozlowski
2026-10-21 16:37 ` Konstantin Ryabitsev
2026-10-21 16:32 ` Laurent Pinchart
2026-10-22 6:57 ` Krzysztof Kozlowski
2026-10-22 7:25 ` Eric Biggers
2026-10-22 8:29 ` Krzysztof Kozlowski
2026-10-22 10:03 ` Laurent Pinchart
2026-10-26 10:40 ` Laurent Pinchart
2026-10-26 10:48 ` Krzysztof Kozlowski
2026-10-26 11:27 ` Mark Brown
2026-10-26 14:02 ` Geert Uytterhoeven
2026-10-26 14:53 ` Laurent Pinchart
2026-10-26 15:37 ` Geert Uytterhoeven
2026-10-26 20:19 ` Laurent Pinchart
2026-10-26 20:51 ` Mark Brown [this message]
2026-10-26 20:12 ` Rob Herring
2026-10-21 14:19 ` Jonathan Corbet
2026-10-21 15:59 ` Krzysztof Kozlowski
2026-10-22 10:04 ` Geert Uytterhoeven
2026-10-22 10:13 ` Krzysztof Kozlowski
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=at-9VwE3BL_3OXNP@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®