From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tony Lindgren <tony@atomide.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Dhruva Gole" <d-gole@ti.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"John Ogness" <john.ogness@linutronix.de>,
"Johan Hovold" <johan@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update TTY layer for lists and recently added files
Date: Tue, 25 Jul 2023 19:28:46 +0200 [thread overview]
Message-ID: <2023072517-onward-payment-569d@gregkh> (raw)
In-Reply-To: <20230724045327.GV5194@atomide.com>
On Mon, Jul 24, 2023 at 07:53:27AM +0300, Tony Lindgren wrote:
> * Andy Shevchenko <andriy.shevchenko@intel.com> [230721 10:19]:
> > On Fri, Jul 21, 2023 at 10:23:32AM +0300, Tony Lindgren wrote:
> > > Add mailing lists for linux-serial and lkml for the TTY layer. And let's
> > > list the recently added files. This makes it easier for get_maintainer.pl
> > > to include linux-serial for patches.
> >
> > Shouldn't serial_* stuff go to the "SERIAL DRIVERS" section?
>
> Not sure if there's some reason we have "TTY LAYER" with serial_core
> files. If not, yeah let's move the serial files.
I'll take this patch, can you send a new one that removes the serial
files from this entry as I don't think they are needed in here anymore.
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-25 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:23 [PATCH] MAINTAINERS: Update TTY layer for lists and recently added files Tony Lindgren
2023-07-21 10:19 ` Andy Shevchenko
2023-07-24 4:53 ` Tony Lindgren
2023-07-25 17:28 ` Greg Kroah-Hartman [this message]
2023-07-25 17:29 ` Greg Kroah-Hartman
2023-07-26 3:30 ` Tony Lindgren
2023-07-26 10:12 ` Jiri Slaby
2023-08-02 12:05 ` Tony Lindgren
2023-08-02 13:49 ` Greg Kroah-Hartman
2023-08-03 5:03 ` Jiri Slaby
2023-08-03 13:39 ` Ilpo Järvinen
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=2023072517-onward-payment-569d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@intel.com \
--cc=bigeasy@linutronix.de \
--cc=d-gole@ti.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).