All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] omap3: isp: fix compiler warning
Date: Wed, 25 May 2011 10:14:46 +0200	[thread overview]
Message-ID: <201105251014.47204.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024D09B451@dbde02.ent.ti.com>

Hi Sanjeev,

On Monday 23 May 2011 20:09:58 Premi, Sanjeev wrote:
> On Monday, May 23, 2011 12:56 AM Laurent Pinchart wrote:
> > On Saturday 21 May 2011 12:55:32 Mauro Carvalho Chehab wrote:
> > > Em 18-05-2011 13:06, Sanjeev Premi escreveu:

[snip]

> > > > @@ -387,7 +387,7 @@ static inline void isp_isr_dbg(struct
> > > > isp_device *isp, u32 irqstatus)
> > > > 
> > > >  	};
> > > >  	int i;
> > > > 
> > > > -	dev_dbg(isp->dev, "");
> > > > +	printk(KERN_DEBUG "%s:\n", dev_driver_string(isp->dev));
> > 
> > The original code doesn't include any \n. Is there a
> > particular reason why you
> > want to add one ?
> 
> [sp] Sorry, that's a mistake out of habit.
>      Another way to fix warning would be to make the string meaningful:
> 
> -	dev_dbg(isp->dev, "");
> +	dev_dbg (isp->dev, "ISP_IRQ:");
> 
>      Is this better?

That looks good to me. I'll queue your patch in my tree (with a space after 
the colon). Thanks.

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2011-05-25  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 16:06 [PATCH] omap3: isp: fix compiler warning Sanjeev Premi
2011-05-21 10:55 ` Mauro Carvalho Chehab
2011-05-22 19:25   ` Laurent Pinchart
2011-05-23 18:09     ` Premi, Sanjeev
2011-05-25  8:14       ` Laurent Pinchart [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=201105251014.47204.laurent.pinchart@ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=premi@ti.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 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.