All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Cleanup of af_unix
Date: Sun, 16 Nov 2008 23:34:42 -0800	[thread overview]
Message-ID: <1226907282.4037.31.camel@localhost> (raw)
In-Reply-To: <4921133D.6070800@cosmosbay.com>

On Mon, 2008-11-17 at 07:46 +0100, Eric Dumazet wrote:
> [PATCH] net: Cleanup of af_unix
> 
> This is a pure cleanup of net/unix/af_unix.c to meet current code style standards
> 
> Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
> --- 
>  net/unix/af_unix.c |  117 ++++++++++++++++++++-----------------------
>  1 files changed, 55 insertions(+), 62 deletions(-)
> plain text document attachment (af_unix_cleanup.patch)
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index 4a39771..58db2a2 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -354,7 +353,7 @@ static void unix_sock_destructor(struct sock *sk)
>  	WARN_ON(!sk_unhashed(sk));
>  	WARN_ON(sk->sk_socket);
>  	if (!sock_flag(sk, SOCK_DEAD)) {
> -		printk("Attempt to release alive unix socket: %p\n", sk);
> +		printk(KERN_DEBUG "Attempt to release alive unix socket: %p\n", sk);
>  		return;
>  	}
>  

Well, perhaps not quite pure.
The KERN_ level selection is debatable.
This could or perhaps should be KERN_INFO.



  parent reply	other threads:[~2008-11-17  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  6:10 [PATCH] net: Cleanup of af_unix Eric Dumazet
2008-11-17  6:32 ` David Miller
2008-11-17  6:46   ` Eric Dumazet
2008-11-17  6:59     ` David Miller
2008-11-17  7:34     ` Joe Perches [this message]
2008-11-17  7:48       ` Eric Dumazet
2008-11-17 19:20       ` Eric Dumazet
2008-11-19 23:48         ` David Miller

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=1226907282.4037.31.camel@localhost \
    --to=joe@perches.com \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --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.