All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	Jiri Kosina <trivial@kernel.org>
Subject: Re: [TRIVIAL PATCH] treewide: Cleanup continuations and remove logging message whitespace
Date: Tue, 26 Apr 2011 10:48:10 +0800	[thread overview]
Message-ID: <20110426024807.GA2751@gmail.com> (raw)
In-Reply-To: <20110425082230.6d656ed0.randy.dunlap@oracle.com>

On Mon, Apr 25, 2011 at 08:22:30AM -0700, Randy Dunlap wrote:
> On Sat, 23 Apr 2011 20:38:19 -0700 Joe Perches wrote:
> 
> > Using C line continuation inside format strings is error prone.
> > Clean up the unintended whitespace introduced by misuse of \.
> > Neaten correctly used line continations as well for consistency.
> > 
> > drivers/scsi/arcmsr/arcmsr_hba.c has these errors as well,
> > but arcmsr needs a lot more work and the driver should likely be
> > moved to staging instead.
> > 
> > Signed-off-by: Joe Perches <joe@perches.com>
>
Acked-by: Harry Wei <harryxiyou@gmail.com>
> 
> 
> Joe,
> Is there a decent fix for this warning in linux-next:
> 
> drivers/tty/n_gsm.c:535: warning: zero-length gnu_printf format string
Hi Randy & Joe,
   I have seen the drivers/tty/n_gsm.c. 
>From line 529 to line 540 in drivers/tty/n_gsm.c like following.

529 static void hex_packet(const unsigned char *p, int len)
530 {
531	int i;
532	for (i = 0; i < len; i++) {
533		if (i && (i % 16) == 0) {
534			pr_cont("\n");
535			pr_debug("");                                                                      
536		}
537		pr_cont("%02X ", *p++);
538	}
539	pr_cont("\n");
540 }

Should we need the line 535? If true, i wanna the function of 
'pr_debug("");'

Thanks.
Harry Wei.

  parent reply	other threads:[~2011-04-26  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24  3:38 [TRIVIAL PATCH] treewide: Cleanup continuations and remove logging message whitespace Joe Perches
2011-04-25 15:22 ` Randy Dunlap
2011-04-25 23:46   ` [PATCH] n_gsm: Use print_hex_dump_bytes Joe Perches
2011-04-26  1:15     ` Randy Dunlap
2011-04-26  2:48   ` Harry Wei [this message]
2011-04-26 16:34     ` [TRIVIAL PATCH] treewide: Cleanup continuations and remove logging message whitespace Randy Dunlap
2011-04-27  1:37       ` Harry Wei
2011-04-26  8:25   ` Jiri Kosina

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=20110426024807.GA2751@gmail.com \
    --to=jiaweiwei.xiyou@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=trivial@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.