From: Shreeya Patel <shreeya.patel23498@gmail.com>
To: boris.brezillon@free-electrons.com, richard@nod.at,
dwmw2@infradead.org, computersforpeace@gmail.com,
marek.vasut@gmail.com, cyrille.pitchen@wedev4u.fr,
outreachy-kernel@googlegroups.com, ezequiel@vanguardiasur.com.ar
Cc: Shreeya Patel <shreeya.patel23498@gmail.com>
Subject: [PATCH NAND 0/5] Replace printk statements with pr_*macros
Date: Fri, 16 Feb 2018 22:20:09 +0530 [thread overview]
Message-ID: <cover.1518797480.git.shreeya.patel23498@gmail.com> (raw)
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.
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
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
next reply other threads:[~2018-02-16 16:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 16:50 Shreeya Patel [this message]
2018-02-16 16:55 ` [PATCH NAND 1/5] mtd/nand: Replace printk with pr_warn Shreeya Patel
2018-02-16 17:08 ` [Outreachy kernel] " Julia Lawall
2018-02-16 17:52 ` Shreeya Patel
2018-02-16 16:57 ` [PATCH NAND 2/5] mtd/nand: Replace printk with pr_notice Shreeya Patel
2018-02-16 17:00 ` [PATCH NAND 3/5] mtd/nand: Replace printk with pr_err Shreeya Patel
2018-02-16 17:03 ` [PATCH NAND 4/5] mtd/nand: Replace printk with pr_info Shreeya Patel
2018-02-16 17:08 ` [PATCH NAND 5/5] mtd/nand: Replace printk with pr_debug Shreeya Patel
2018-02-16 17:19 ` [PATCH NAND 0/5] Replace printk statements with pr_*macros Richard Weinberger
2018-02-16 17:24 ` Ezequiel Garcia
2018-02-16 17:25 ` Ezequiel Garcia
2018-02-16 17:58 ` Richard Weinberger
2018-02-16 18:15 ` Boris Brezillon
2018-02-16 18:48 ` [Outreachy kernel] " Greg KH
2018-02-16 18:54 ` Julia Lawall
2018-02-16 18:00 ` Boris Brezillon
2018-02-16 17:19 ` 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
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=cover.1518797480.git.shreeya.patel23498@gmail.com \
--to=shreeya.patel23498@gmail.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=marek.vasut@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.