From: Conor Dooley <conor@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the robh/linux for-next branch
Date: Thu, 1 Oct 2026 19:58:09 +0100 [thread overview]
Message-ID: <20261001-stride-trailside-d533de737a6e@spud> (raw)
In-Reply-To: <20261001112526.3822682-1-matthias.goergens@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Thu, Oct 01, 2026 at 07:25:26PM +0800, Matthias Goergens wrote:
> Hi Rob,
>
> > Is doing this preferred over changing what HEAD points to? Happy to do either.
>
> Neither, it turns out; please drop the patch and leave HEAD as it is.
>
> The motivation was Sashiko, which reviewed against the default branch
> of the tree in T: even when that branch was far behind. Your master
> follows mainline closely; while it is at the same commit, as it is
> today, Sashiko reviews against mainline in effect. When it falls
> behind, Sashiko now skips it (since 28 September) and uses linux-next,
> which has your for-next and dt/linus. As Greg pointed out on the tty
> patch, a single branch in T: could not cover both anyway. So there
> is nothing for you to change.
Does this mean that you're dropping and/or reverting all patches of this
kind?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-01 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 10:59 [PATCH] MAINTAINERS: name the robh/linux for-next branch Matthias Goergens
2026-09-28 13:15 ` Rob Herring
2026-10-01 11:25 ` Matthias Goergens
2026-10-01 18:58 ` Conor Dooley [this message]
2026-10-02 4:25 ` Matthias Goergens
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=20261001-stride-trailside-d533de737a6e@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=matthias.goergens@gmail.com \
--cc=robh@kernel.org \
--cc=saravanak@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