From: david.woodhouse@intel.com (David Woodhouse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/20] mtd: pxa3xx_nand: add debug messege
Date: Fri, 14 May 2010 09:35:19 +0100 [thread overview]
Message-ID: <1273826119.9999.1634.camel@macbook.infradead.org> (raw)
In-Reply-To: <4BED07BD.7090403@pengutronix.de>
On Fri, 2010-05-14 at 09:20 +0100, Marc Kleine-Budde wrote:
>
> If you really need to get this in mainline, try using pr_debug() for
> this, add
>
> #if PXA3XX_NAND_DEBUG
> #define DEBUG
> #endif
>
> to activate debugging.
I _wish_ we could have a per-device 'debug' flag, and dev_dbg() would
work based on that. We should also be able to compile it out completely,
of course.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse at intel.com Intel Corporation
prev parent reply other threads:[~2010-05-14 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 6:19 [PATCH 11/20] mtd: pxa3xx_nand: add debug messege Haojian Zhuang
2010-05-14 8:20 ` Marc Kleine-Budde
2010-05-14 8:35 ` David Woodhouse [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=1273826119.9999.1634.camel@macbook.infradead.org \
--to=david.woodhouse@intel.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).