public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@infradead.org>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [RPC] OLPC tablet input driver.
Date: Tue, 29 Aug 2006 21:45:43 -0700	[thread overview]
Message-ID: <20060830044543.GA14738@kroah.com> (raw)
In-Reply-To: <20060829084443.GA4187@aehallh.com>

On Tue, Aug 29, 2006 at 04:44:43AM -0400, Zephaniah E. Hull wrote:
> On Tue, Aug 29, 2006 at 10:10:19AM +0200, Arjan van de Ven wrote:
> > > +#undef DEBUG
> > > +#ifdef DEBUG
> > > +#define dbg(format, arg...) printk(KERN_INFO "olpc.c(%d): " format "\n", __LINE__, ## arg)
> > > +#else
> > > +#define dbg(format, arg...) do {} while (0)
> > > +#endif
> > 
> > why not use pr_debug or even dev_debug() ?
> > Those already have this ifdef included
> 
> I was not thinking of them at the time, however dev_dbg is not an option
> because we do not have a struct device at hand when we want to print
> some debugging lines.

Then use it for the majority of the places where you do have it, and do
pr_debug() when you do not.

> pr_debug might work, but I would rather have file and line already
> there.
> 
> Though, admittedly, that would be a better argument if it used __FILE__
> there instead of hard coding it.

__FILE__ will return you a full path, which is what I do not think you
want...

thanks,

greg k-h

  parent reply	other threads:[~2006-08-30  4:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29  7:33 [RPC] OLPC tablet input driver Zephaniah E. Hull
2006-08-29  8:10 ` Arjan van de Ven
2006-08-29  8:44   ` Zephaniah E. Hull
2006-08-29 12:29     ` Dmitry Torokhov
2006-08-30  4:45     ` Greg KH [this message]
2006-08-29  8:55 ` Komal Shah
2006-08-29 10:40   ` Zephaniah E. Hull
2006-08-29 12:26     ` Dmitry Torokhov
2006-08-29  9:00 ` Komal Shah
2006-08-29 12:53 ` Dmitry Torokhov
2006-08-29 14:35   ` Zephaniah E. Hull
2006-08-29 15:12     ` Dmitry Torokhov
2006-09-10 20:10 ` [RFC] OLPC tablet input driver, take two Zephaniah E. Hull
2006-09-10 22:19   ` Dmitry Torokhov
2006-09-11 18:27     ` Zephaniah E. Hull
2006-09-11 19:01       ` Dmitry Torokhov
2006-09-11 19:03         ` Zephaniah E. Hull
2006-09-11 19:02   ` [RFC] OLPC tablet input driver, take three Zephaniah E. Hull
2006-09-11 19:10     ` Dmitry Torokhov
2006-09-12 19:39       ` Zephaniah E. Hull
2006-09-12 19:58         ` Dmitry Torokhov
2006-11-08 12:04 ` [RPC] OLPC tablet input driver Vojtech Pavlik

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=20060830044543.GA14738@kroah.com \
    --to=greg@kroah.com \
    --cc=arjan@infradead.org \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.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