From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: "Joe Perches" <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, "Greg KH" <gregkh@suse.de>,
"Jeff Garzik" <jeff@garzik.org>,
"Tony Luck" <tony.luck@intel.com>,
"Jiri Slaby" <jirislaby@gmail.com>,
"Roland Dreier" <rolandd@cisco.com>,
"David Brownell" <dbrownell@users.sourceforge.net>,
"James Smart" <james.smart@emulex.com>,
"Hansjoerg Lipp" <hjlipp@web.de>,
"Jean Delvare" <khali@linux-fr.org>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
"Jeremy Fitzhardinge" <jeremy@xensource.com>
Subject: Re: [PATCH] Add missing newlines to some uses of dev_<level> messages
Date: Tue, 7 Aug 2007 20:00:24 -0700 [thread overview]
Message-ID: <29495f1d0708072000m3d6d6febpad0db101ed48aa24@mail.gmail.com> (raw)
In-Reply-To: <1186535381.11897.29.camel@localhost>
On 8/7/07, Joe Perches <joe@perches.com> wrote:
> Found these while looking at printk uses.
>
> Add missing newlines to dev_<level> uses
> Add missing KERN_<level> prefixes to multiline dev_<level>s
> Fixed a wierd->weird spelling typo
> Added a newline to a printk
I think these should have been split logically into 4 groups of
patches (except perhaps where they touched the same file for the first
two and the last).
The third type should go through trivial.
And they should have been split logically by subsystem, most likely?
<snip diffstat>
> diff --git a/arch/ia64/sn/kernel/xpnet.c b/arch/ia64/sn/kernel/xpnet.c
> index e58fcad..a5df672 100644
> --- a/arch/ia64/sn/kernel/xpnet.c
> +++ b/arch/ia64/sn/kernel/xpnet.c
> @@ -269,8 +269,9 @@ xpnet_receive(partid_t partid, int channel, struct xpnet_message *msg)
> skb->protocol = eth_type_trans(skb, xpnet_device);
> skb->ip_summed = CHECKSUM_UNNECESSARY;
>
> - dev_dbg(xpnet, "passing skb to network layer; \n\tskb->head=0x%p "
> - "skb->data=0x%p skb->tail=0x%p skb->end=0x%p skb->len=%d\n",
> + dev_dbg(xpnet, "passing skb to network layer\n"
> + KERN_DEBUG "\tskb->head=0x%p skb->data=0x%p skb->tail=0x%p "
> + "skb->end=0x%p skb->len=%d\n",
> (void *)skb->head, (void *)skb->data, skb_tail_pointer(skb),
> skb_end_pointer(skb), skb->len);
<snip>
I'm not a maintainer of any code by any means, but it seems odd,
redundant and visually confusing to me to use the dev_dbg() function
and have KERN_DEBUG's inside the string -- makes me question every
time why there isn't one for the first line too.
Perhaps these multi-line debug statements should simply be split into
multiple dev_dbg() calls? Similar for the other dev_ functions. I
think it might look cleaner, at least. Just my two cents, not a NAK or
anything.
Thanks,
Nish
next prev parent reply other threads:[~2007-08-08 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 1:09 Joe Perches
2007-08-08 1:34 ` James Smart
2007-08-08 2:01 ` Jeff Garzik
2007-08-08 3:00 ` Nish Aravamudan [this message]
2007-08-10 20:34 ` Jean Delvare
2007-08-09 2:52 ` Mark M. Hoffman
2007-08-09 6:30 ` David Brownell
2007-08-09 6:33 ` Jiri Slaby
2007-08-11 7:23 ` Jean Delvare
2007-08-11 19:31 ` David Brownell
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=29495f1d0708072000m3d6d6febpad0db101ed48aa24@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=hjlipp@web.de \
--cc=james.smart@emulex.com \
--cc=jeff@garzik.org \
--cc=jeremy@xensource.com \
--cc=jirislaby@gmail.com \
--cc=joe@perches.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhoffman@lightlink.com \
--cc=rolandd@cisco.com \
--cc=tony.luck@intel.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®