From: "Stéphane Pajot" <pajot.stephane@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: rdunlap@xenotime.net, fmhess@users.sourceforge.net,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: fix trailing whitespace and quoted string split across lines in ni_labpc.c
Date: Tue, 24 Apr 2012 21:27:09 +0200 [thread overview]
Message-ID: <20120424192709.GA4717@stef-pc> (raw)
In-Reply-To: <20120424184642.GA20004@kroah.com>
On Tue, Apr 24, 2012 at 11:46:42AM -0700, Greg KH wrote:
> On Tue, Apr 24, 2012 at 06:50:10PM +0200, Stéphane Pajot wrote:
> > This is a patch to the ni_labpc.c file that fixes up trailing whitespace error and quoted string split across lines warning
> > found by the checkpatch.pl tool
>
> Please only fix one type of thing per patch, so this should be a two
> patch series at the least.
Ok for that.
>
> But...
>
> > @@ -738,7 +738,7 @@ static int labpc_attach(struct comedi_device *dev, struct comedi_devconfig *it)
> > irq = it->options[1];
> > dma_chan = it->options[2];
> > #else
> > - printk(KERN_ERR " this driver has not been built with ISA DMA "
> > + printk(KERN_ERR " this driver has not been built with ISA DMA\n"
> > "support.\n");
>
> What? Why did you do this? Do you understand what you just did to the
> message printed out?
... It was just to patch this "quoted string split across lines
warning", i saw this solution on the web. Now i think i understand that
i cannot modify AT ALL a printk(KERN_ERR* even if it's just with a \n ?
Stef
>
> greg k-h
next prev parent reply other threads:[~2012-04-24 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335286210-3150-1-git-send-email-pajot.stephane@gmail.com>
2012-04-24 18:46 ` [PATCH] Staging: comedi: fix trailing whitespace and quoted string split across lines in ni_labpc.c Greg KH
2012-04-24 19:27 ` Stéphane Pajot [this message]
2012-04-24 20:00 ` Greg KH
2012-04-24 20:03 ` Dan Carpenter
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=20120424192709.GA4717@stef-pc \
--to=pajot.stephane@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.