public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver Core update for 2.6.4-rc1
Date: Wed, 3 Mar 2004 22:24:54 +0000	[thread overview]
Message-ID: <20040303222454.A15007@flint.arm.linux.org.uk> (raw)
In-Reply-To: <10782873993395@kroah.com>; from greg@kroah.com on Tue, Mar 02, 2004 at 08:16:39PM -0800

On Tue, Mar 02, 2004 at 08:16:39PM -0800, Greg KH wrote:
> ChangeSet 1.1612.24.4, 2004/03/02 16:39:36-08:00, greg@kroah.com
> 
> Driver core: add CONFIG_DEBUG_DRIVER to help track down driver core bugs easier.

Wouldn't a cleaner way to do this be to add -DDEBUG to EXTRA_CFLAGS
in the makefile if CONFIG_DEBUG_DRIVER is set, and remove the #undef
DEBUG statements in each .c file?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-03-03 22:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  4:14 [BK PATCH] Driver Core update for 2.6.4-rc1 Greg KH
2004-03-03  4:16 ` [PATCH] " Greg KH
2004-03-03  4:16   ` Greg KH
2004-03-03  4:16     ` Greg KH
2004-03-03  4:16       ` Greg KH
2004-03-03  4:16         ` Greg KH
2004-03-03  4:16           ` Greg KH
2004-03-03  4:16             ` Greg KH
2004-03-03  4:16               ` Greg KH
2004-03-03  4:16                 ` Greg KH
2004-03-03  4:16                   ` Greg KH
2004-03-03 22:24                     ` Russell King [this message]
2004-03-03 23:06                       ` Greg KH
2004-03-03  8:00             ` Christoph Hellwig
2004-03-03 15:07               ` Greg KH
2004-03-03 15:13                 ` Christoph Hellwig
2004-03-03 15:19                   ` Greg KH

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=20040303222454.A15007@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.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