From: Joe Perches <joe@perches.com>
To: David Howells <dhowells@redhat.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-afs <linux-afs@lists.infradead.org>
Subject: Re: [PATCH] rxrpc: Neaten logging macros and add KERN_DEBUG logging level
Date: Thu, 30 Nov 2017 11:46:04 -0800 [thread overview]
Message-ID: <1512071164.19952.129.camel@perches.com> (raw)
In-Reply-To: <25765.1512070491@warthog.procyon.org.uk>
On Thu, 2017-11-30 at 19:34 +0000, David Howells wrote:
> Joe Perches <joe@perches.com> wrote:
>
> > There is no listed rxrpc maintainer.
>
> There's a script in the kernel called get_maintainer.pl which you might find
> of use:
Yeah, I've heard of it. I also wrote it btw.
> warthog>./scripts/get_maintainer.pl net/rxrpc/
> "David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING [GENERAL],commit_signer:23/74=31%)
> David Howells <dhowells@redhat.com> (commit_signer:64/74=86%,authored:60/74=81%)
> netdev@vger.kernel.org (open list:NETWORKING [GENERAL])
> linux-kernel@vger.kernel.org (open list)
The script I use to send patches does not cc
patch authors as, based on my history
sending patches, most to many of them do not
want to see patches.
> It would seem a good idea to cc me, as the one with the largest "authored"
> also.
Perhaps a better idea would be to have an
rxrpc section in the MAINTAINERS file.
cheers, Joe
prev parent reply other threads:[~2017-11-30 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 16:21 [PATCH] rxrpc: Neaten logging macros and add KERN_DEBUG logging level Joe Perches
2017-11-30 17:31 ` David Miller
2017-11-30 18:06 ` Joe Perches
2017-11-30 18:13 ` David Miller
2017-11-30 18:18 ` Joe Perches
2017-11-30 18:19 ` David Miller
2017-11-30 19:34 ` David Howells
2017-11-30 19:46 ` Joe Perches [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=1512071164.19952.129.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.