mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Eric Biggers <ebiggers@kernel.org>,
	linux-doc@vger.kernel.org, workflows@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] docs: submitting-patches: Require base tree information
Date: Wed, 21 Oct 2026 08:19:48 -0600	[thread overview]
Message-ID: <87y0br3zln.fsf@trenco.lwn.net> (raw)
In-Reply-To: <363b228a-7e96-481a-b70f-195ba55d025e@kernel.org>

Krzysztof Kozlowski <krzk@kernel.org> writes:

> For many of my contributions base is obvious and not needed to be
> explicitly defined. For all the patches I accept, answer is the same -
> base is either obvious or if not and patch does not apply, then the base
> does not matter.
>
> Requiring it is just bureaucracy without actual benefit.
>
> The only benefit would be if maintainer COULD change its base to apply
> some patch with odd base... but this cannot happen. Maintainer base is
> fixed - it's the HEAD of his development branch for given category of
> commits (e.g. DTS branch for SoC maintainers).

I fairly routinely get docs patches that don't apply to docs-next; when
I'm in the mood, I'll try to figure what they *do* apply to, then
cherry-pick them over.  Base information would make that process easier,
and even automatable.

Thanks,

jon

  parent reply	other threads:[~2026-10-21 14:19 UTC|newest]

Thread overview: 16+ 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 14:19   ` Jonathan Corbet [this message]
2026-10-21 15:59     ` 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=87y0br3zln.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=ebiggers@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=krzk@kernel.org \
    --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®