From: Krzysztof Kozlowski <krzk@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-doc@vger.kernel.org, workflows@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: Require base tree information
Date: Wed, 21 Oct 2026 08:47:39 +0200 [thread overview]
Message-ID: <24f76150-83b3-4cf9-a1f4-995f703e7902@kernel.org> (raw)
In-Reply-To: <20261021064456.GB31908@sol>
On 21/10/2026 08:44, Eric Biggers wrote:
>>> (for linux-next-20261020:)
>>> base-commit: 053966c344dbd346e71305f530e91ea77916189f
>>> base-tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>
>> According to commit msg which claims that without base information "nor
>> can they be accepted. "
>
> I actually wrote:
>
> Many patches still don't include base tree information and can't be
> applied. Such patches can't be properly reviewed or tested, nor can
> they be accepted.
>
> So it's about patches that can't be applied due to lack of base tree
> information (due to the obvious guess not working). Not merely the lack
> of such information by itself.
>
I have troubles in such case understanding that part of your commit msg.
I maintain a few different trees, accept patches there and send pull
requests to a few different upstream maintainers. I never had any
problem with applying a patch due to missing base. IOW, having there a
base tree information would not solve anything in "applied" or
"accepted" part.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-21 6:47 UTC|newest]
Thread overview: 11+ 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 [this message]
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
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=24f76150-83b3-4cf9-a1f4-995f703e7902@kernel.org \
--to=krzk@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=konstantin@linuxfoundation.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®