From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the gregkh/tty tty-next branch
Date: Mon, 28 Sep 2026 13:44:56 +0200 [thread overview]
Message-ID: <2026092800-clustered-unlighted-a54a@gregkh> (raw)
In-Reply-To: <20260928105940.2186243-1-matthias.goergens@gmail.com>
On Mon, Sep 28, 2026 at 06:59:40PM +0800, Matthias Goergens wrote:
> The T: entries for 8250/16?50 (AND CLONE UARTS) SERIAL DRIVER and TTY
> LAYER AND SERIAL DRIVERS name gregkh/tty without a branch. The
> repository's HEAD points to branch main, which mainline already
> contains. linux-next merges the tty-next branch of this repository
> (Next/Trees). Name that branch in both entries.
>
> Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
> ---
> This is part of a cleanup of all T: entries whose repository HEAD is
> not where development happens: one patch per repository, sent in small
> batches. The plan is at [1], and why it goes out in batches at [2].
Why is -next the valid branch here? I was wondering how you were going
to deal with all of this...
Hint, -linus is for bugfixes "now" and -next is for the next release.
So why pick just one for this entry? 50% of the chance of getting it
right?
{sigh}
greg k-h
prev parent reply other threads:[~2026-09-28 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 10:59 Matthias Goergens
2026-09-28 11:44 ` Greg Kroah-Hartman [this message]
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=2026092800-clustered-unlighted-a54a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthias.goergens@gmail.com \
/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®