From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 00/11] mtd: change printks to pr_*
Date: Wed, 20 Jul 2011 08:50:38 +0300 [thread overview]
Message-ID: <1311141042.20738.158.camel@sauron> (raw)
In-Reply-To: <1311095176-5407-1-git-send-email-computersforpeace@gmail.com>
On Tue, 2011-07-19 at 10:06 -0700, Brian Norris wrote:
> We've had quite some discussion about whether to use printk, pr_*, or
> dev_* functions for printing info, error, and debugging messages.
> Unfortunately, MTD doesn't quite have a nice device model, so we can't
> always use dev_* to print nice device information. This patch series
> mostly transitions the NAND subsystem to use pr_* functions, which are
> a little more brief and slightly more flexible than printk.
>
> Along the way, we've dumped a lot of old DEBUG() code that was written
> specifically for MTD in favor of dynamic debugging. I tried killing the
> corresponding Kconfig options as well. Not sure if patches 9 and 10 are
> necessary.
>
> These patches apply on top of l2-mtd-2.6.git
>
> Brian
>
> Brian Norris (11):
> mtd: nand: change KERN_DEBUG to KERN_INFO
> mtd: nand: convert printk() to pr_*()
> mtd: nand: style fixups in pr_* messages
> mtd: replace DEBUG() with pr_debug()
> mtd: cleanup style on pr_debug messages
> mtd: pcmciamtd: remove custom DEBUG() function
> mtd: remove CONFIG_MTD_DEBUG
> mtd: cleanup last uses of MTD_DEBUG config macros
> arch: remove references to CONFIG_MTD_DEBUG and
> CONFIG_MTD_DEBUG_VERBOSE
> arch: remove references to CONFIG_MTD_PARTITIONS
> mtd: Kbuild: remove reference to MTD_PARTITIONS
Pushed the series to the l2-mtd-2.6.git tree, except of the 2 "arch:
blah" patches. I think for defconfigs the practice is that the owners
update them themselves. People who use the defconfigs will not have
problems anyway because a non-existing Kconfig options like
CONFIG_MTD_PARTITIONS will be ignored.
Besides, there was a big hassle around defconfigs recently. In short -
Linus did not like that ARM defconfigs are constanly changing and add a
lot of noise.
Thanks!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2011-07-20 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 17:06 [PATCH 00/11] mtd: change printks to pr_* Brian Norris
2011-07-19 17:06 ` [PATCH 01/11] mtd: nand: change KERN_DEBUG to KERN_INFO Brian Norris
2011-07-19 17:06 ` [PATCH 02/11] mtd: nand: convert printk() to pr_*() Brian Norris
2011-07-19 17:06 ` [PATCH 03/11] mtd: nand: style fixups in pr_* messages Brian Norris
2011-07-19 17:06 ` [PATCH 04/11] mtd: replace DEBUG() with pr_debug() Brian Norris
2011-07-19 17:06 ` [PATCH 05/11] mtd: cleanup style on pr_debug messages Brian Norris
2011-07-19 17:06 ` [PATCH 06/11] mtd: pcmciamtd: remove custom DEBUG() function Brian Norris
2011-07-19 17:06 ` [PATCH 07/11] mtd: remove CONFIG_MTD_DEBUG Brian Norris
2011-07-19 17:06 ` [PATCH 08/11] mtd: cleanup last uses of MTD_DEBUG config macros Brian Norris
2011-07-19 17:06 ` [PATCH 09/11] arch: remove references to CONFIG_MTD_DEBUG and CONFIG_MTD_DEBUG_VERBOSE Brian Norris
2011-07-19 17:06 ` [PATCH 10/11] arch: remove references to CONFIG_MTD_PARTITIONS Brian Norris
2011-07-19 17:06 ` [PATCH 11/11] mtd: Kbuild: remove reference to MTD_PARTITIONS Brian Norris
2011-07-20 5:50 ` Artem Bityutskiy [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=1311141042.20738.158.camel@sauron \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@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