From: Greg KH <greg@kroah.com>
To: Ravishankar K Mallikarjunayya <ravishankar.km@greenturtles.in>
Cc: gregkh@suse.de, wfp5p@virginia.edu, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Staging: comedi: fix printk issue in cb_pcidda.c
Date: Fri, 9 Sep 2011 13:25:06 -0700 [thread overview]
Message-ID: <20110909202506.GA3018@kroah.com> (raw)
In-Reply-To: <1314791612-2724-1-git-send-email-ravishankar.km@greenturtles.in>
On Wed, Aug 31, 2011 at 05:23:32PM +0530, Ravishankar K Mallikarjunayya wrote:
> This is a patch to the cb_pcidda.c file that fixes up a printk warning found by the checkpatch.pl tool
Please wrap your changelog comment at 72 columns, like sane people do.
>
> Signed-off-by: Ravishankar K Mallikarjunayya <ravishankar.km@greenturtles.in>
> ---
> drivers/staging/comedi/drivers/cb_pcidda.c | 23 ++++++++++++-----------
> 1 files changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers/cb_pcidda.c b/drivers/staging/comedi/drivers/cb_pcidda.c
> index 49102b3..661e945 100644
> --- a/drivers/staging/comedi/drivers/cb_pcidda.c
> +++ b/drivers/staging/comedi/drivers/cb_pcidda.c
> @@ -282,7 +282,7 @@ static int cb_pcidda_attach(struct comedi_device *dev,
> struct pci_dev *pcidev = NULL;
> int index;
>
> - printk("comedi%d: cb_pcidda: ", dev->minor);
> + pr_info("comedi%d: cb_pcidda: ", dev->minor);
If you have a device pointer, then use dev_info() here.
Same goes for the other changes in this series. Use the proper dev_*
macros.
And what is up with your patch numbering scheme? Please send me all of
the patches, not a bunch of [1/1] and the like, in one set, all linked
together properly like git-send-email will do.
greg k-h
prev parent reply other threads:[~2011-09-09 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 1/2]Staging: comedi: fix printk issue in cb_pcidda.c>
2011-08-31 11:53 ` [PATCH 1/2] Staging: comedi: fix printk issue in cb_pcidda.c Ravishankar K Mallikarjunayya
2011-09-09 20:25 ` Greg KH [this message]
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=20110909202506.GA3018@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ravishankar.km@greenturtles.in \
--cc=wfp5p@virginia.edu \
/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