From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Trevor Woerner <twoerner@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jiri Kosina <trivial@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Yorick de Wid <yorickdewid@users.noreply.github.com>,
Dan Williams <dan.j.williams@intel.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] coding-style.rst: trivial: fix location of driver model macros
Date: Tue, 26 Oct 2021 08:27:43 -0700 [thread overview]
Message-ID: <58650d3729a5b3a8bc86037757bccda5cc254e3f.camel@perches.com> (raw)
In-Reply-To: <fe86efbd-4e03-76c8-55cf-dabd33e85823@infradead.org>
On Tue, 2021-10-26 at 08:18 -0700, Randy Dunlap wrote:
> On 10/26/21 8:10 AM, Miguel Ojeda wrote:
> > On Tue, Oct 26, 2021 at 4:44 PM Trevor Woerner <twoerner@gmail.com> wrote:
> > >
> > > get_maintainer.pl didn't add Andrew back then on my patch and still doesn't
> > > even now. Maybe the MAINTAINERS file needs an update if Andrew is to be
> > > included on trivial/documentation patches?
> >
> > I mentioned Andrew because he does the hard job of being a backup for
> > everything and everyone, but normally you should try to put the actual
> > maintainer first in the `To` field and/or trivial@kernel.org.
>
> I think that we decided to stop using trivial@kernel.org for new patches
> a few months ago...
Dunno who the "we" is but then maybe this is appropriate:
---
MAINTAINERS | 6 ------
1 file changed, 6 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 869e6cc6366bc..8c933736bb412 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19282,12 +19282,6 @@ W: https://github.com/srcres258/linux-doc
T: git git://github.com/srcres258/linux-doc.git doc-zh-tw
F: Documentation/translations/zh_TW/
-TRIVIAL PATCHES
-M: Jiri Kosina <trivial@kernel.org>
-S: Maintained
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git
-K: ^Subject:.*(?i)trivial
-
TTY LAYER
M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
M: Jiri Slaby <jirislaby@kernel.org>
next prev parent reply other threads:[~2021-10-26 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 18:40 Trevor Woerner
2021-04-23 18:54 ` Shuah Khan
2021-04-23 19:14 ` Miguel Ojeda
[not found] ` <CAHUNapQfFBcqrX7MvUvq8qbPgk2bPu-h3+9NxAUFpRtpOGFODw@mail.gmail.com>
2021-10-26 12:47 ` Miguel Ojeda
2021-10-26 14:44 ` Trevor Woerner
2021-10-26 15:10 ` Miguel Ojeda
2021-10-26 15:18 ` Randy Dunlap
2021-10-26 15:27 ` Joe Perches [this message]
2021-10-26 23:49 ` Randy Dunlap
2021-10-26 15:28 ` Miguel Ojeda
2021-10-26 15:37 ` Joe Perches
2021-10-26 21:21 ` Trevor Woerner
2021-10-26 15:41 ` Jonathan Corbet
2021-10-26 21:23 ` Trevor Woerner
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=58650d3729a5b3a8bc86037757bccda5cc254e3f.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=geert@linux-m68k.org \
--cc=grandmaster@al2klimov.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=trivial@kernel.org \
--cc=twoerner@gmail.com \
--cc=yorickdewid@users.noreply.github.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®