All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	dhowells@redhat.com, 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 10:06:51 -0800	[thread overview]
Message-ID: <1512065211.19952.112.camel@perches.com> (raw)
In-Reply-To: <20171130.123117.1742804316627893121.davem@davemloft.net>

On Thu, 2017-11-30 at 12:31 -0500, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Thu, 30 Nov 2017 08:21:14 -0800
> 
> > When enabled, the current debug logging does not have a KERN_<LEVEL>.
> > Add KERN_DEBUG to the logging macros.
> > 
> > Miscellanea:
> > 
> > o Remove #define redundancy and neaten the macros a bit
> > 
> > Signed-off-by: Joe Perches <joe@perches.com>
> 
> Please also CC: the proper mailing list and maintainer for rxrpc.
> 
> The MAINTAINERS entry for rxrpc needs to include more than just
> net/rxrpc/af_rxrpc.c, David please fix this up as I know Joe is going
> to use the excuse that he didn't CC: you and the AFS list because of
> this.

There is no listed rxrpc maintainer.

David Howells entry is:

AFS FILESYSTEM & AF_RXRPC SOCKET DOMAIN
M:	David Howells <dhowells@redhat.com>
L:	linux-afs@lists.infradead.org
S:	Supported
F:	fs/afs/
F:	include/net/af_rxrpc.h
F:	net/rxrpc/af_rxrpc.c
W:	https://www.infradead.org/~dhowells/kafs/

which seems pretty specific to AFS and its rxrpc kernel interface.

Excuse is probably the wrong word here David.
Rationale maybe...

cheers, Joe

  reply	other threads:[~2017-11-30 18:06 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 [this message]
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

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=1512065211.19952.112.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.