From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Shreeya Patel <shreeya.patel23498@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
outreachy-kernel <outreachy-kernel@googlegroups.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH NAND 0/5] Replace printk statements with pr_*macros
Date: Fri, 16 Feb 2018 18:45:37 +0100 [thread overview]
Message-ID: <20180216184537.3cd1e414@bbrezillon> (raw)
In-Reply-To: <CAAEAJfAg_hei2PF37_oX2tf+Mv43ye-nEOt+KRVFerp1Jfzn2Q@mail.gmail.com>
On Fri, 16 Feb 2018 14:19:41 -0300
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> wrote:
> Hi Shreeya,
>
> Thanks for the contribution.
>
> On 16 February 2018 at 13:50, Shreeya Patel
> <shreeya.patel23498@gmail.com> wrote:
> > This patchset removes all the log levels i.e. KERN_WARN,
> > KERN_NOTICE, KERN_ERR, KERN_INFO, KERN_DEBUG used in the printk
> > statements and replaces the printk statements with appropriate
> > pr_*macros.
> > According to the kernel coding style, pr_*macro is the preferred
> > way to print the message.
> >
>
> So, two things to begin with.
>
> First of all, despite this contribution being part of outreachy,
> I believe you can include mailing lists in your case.
>
> In other words, don't use the "nol" option in get_maintainer
> script and Cc the MTD mailing list: linux-mtd at lists.infradead.org.
>
> >
> > Shreeya Patel (5):
> > mtd/nand: Replace printk with pr_warn
> > mtd/nand: Replace printk with pr_notice
> > mtd/nand: Replace printk with pr_err
> > mtd/nand: Replace printk with pr_info
> > mtd/nand: Replace printk with pr_debug
Nitpick: prefix should be "mtd: nand: ".
> >
>
> This is a non-usual split. We usually split patches per-driver,
> instead of grouping all the pr_{} of a given type together.
I agree.
>
> Can you re-do the series? Grouping the changes per-driver,
> i.e. all the pr_{} changes in cafe_nand.c together, and so on.
Actually, for such simple/automatic changes you can even group things
in a single patch. I'm fine either way.
>
> > drivers/mtd/nand/ams-delta.c | 4 +--
> > drivers/mtd/nand/cafe_nand.c | 4 +--
> > drivers/mtd/nand/cs553x_nand.c | 8 ++---
> > drivers/mtd/nand/diskonchip.c | 76 +++++++++++++++++++++-------------------
> > drivers/mtd/nand/fsl_elbc_nand.c | 4 +--
> > drivers/mtd/nand/fsl_ifc_nand.c | 2 +-
> > drivers/mtd/nand/mxc_nand.c | 2 +-
> > drivers/mtd/nand/nand_bch.c | 12 +++----
> > drivers/mtd/nand/nandsim.c | 10 +++---
> > drivers/mtd/nand/r852.c | 2 +-
> > drivers/mtd/nand/r852.h | 6 ++--
> > drivers/mtd/nand/sh_flctl.c | 2 +-
> > drivers/mtd/nand/sm_common.c | 5 ++-
> > 13 files changed, 70 insertions(+), 67 deletions(-)
> >
> > --
> > 2.7.4
> >
>
>
>
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-16 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1518797480.git.shreeya.patel23498@gmail.com>
2018-02-16 17:19 ` [PATCH NAND 0/5] Replace printk statements with pr_*macros Ezequiel Garcia
2018-02-16 17:23 ` [Outreachy kernel] " Julia Lawall
2018-02-16 17:26 ` Ezequiel Garcia
2018-02-16 17:48 ` Boris Brezillon
2018-02-16 17:59 ` Shreeya Patel
[not found] ` <1518976870.2784.4.camel@gmail.com>
[not found] ` <20180218191347.76f4a287@bbrezillon>
[not found] ` <1518978365.2969.6.camel@gmail.com>
2018-02-18 20:09 ` Boris Brezillon
2018-02-18 20:20 ` Shreeya Patel
2018-02-18 20:30 ` Shreeya Patel
2018-02-16 17:35 ` Shreeya Patel
2018-02-16 17:45 ` Boris Brezillon [this message]
[not found] ` <1963507.Bpu1nn9g4S@blindfold>
[not found] ` <CAAEAJfD6CbWOfrYOY4QDW0tte-yOebcZTGjUDQhR8uE+fsOs3w@mail.gmail.com>
2018-02-16 17:25 ` Ezequiel Garcia
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=20180216184537.3cd1e414@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=richard@nod.at \
--cc=shreeya.patel23498@gmail.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