mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] apparent typo in ixgb.h, "_DEBUG_DRIVER_" looks wrong
Date: Tue, 10 Oct 2006 05:28:40 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610100522240.6146@localhost.localdomain> (raw)
In-Reply-To: <20061010091501.GA5369@martell.zuzino.mipt.ru>

On Tue, 10 Oct 2006, Alexey Dobriyan wrote:

> On Tue, Oct 10, 2006 at 02:27:34AM -0400, Robert P. J. Day wrote:
> > I'm *guessing* that "_DEBUG_DRIVER_" should really be
> > "DEBUG_DRIVER" here, since there is no other occurrence of the
> > former anywhere in the source tree.
>
> Since it's debugging guard, underscored or not... doesn't matter.
> Convert to pr_debug or dev_dbg of you want to deal with it.
>
> > --- a/drivers/net/ixgb/ixgb.h
> > +++ b/drivers/net/ixgb/ixgb.h
> > @@ -77,7 +77,7 @@ #include "ixgb_hw.h"
> >  #include "ixgb_ee.h"
> >  #include "ixgb_ids.h"
> >
> > -#ifdef _DEBUG_DRIVER_
> > +#ifdef DEBUG_DRIVER
> >  #define IXGB_DBG(args...) printk(KERN_DEBUG "ixgb: " args)
> >  #else
> >  #define IXGB_DBG(args...)

but what you're suggesting is not equivalent.  i submitted that patch
to fix what *seems* to be an obvious, innocuous typo, to bring that
one header file into sync with the rest of the source tree, nothing
more.

if all debugging should now use either of pr_debug() or dev_dbg(),
that's fine but i notice that both of those macros will be defined
only if "DEBUG" is defined, not "DEBUG_DRIVER".  so making the change
you suggest would *not* be a trivial change.

what's the current standard for debugging directives in the kernel?

rday

  reply	other threads:[~2006-10-10  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  6:27 Robert P. J. Day
2006-10-10  9:15 ` Alexey Dobriyan
2006-10-10  9:28   ` Robert P. J. Day [this message]
2006-10-10 10:01     ` Arjan van de Ven

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=Pine.LNX.4.64.0610100522240.6146@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®