From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Ray Zhang <sgzhang@google.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mtd: mtdoops: change printk() to counterpart pr_ functions
Date: Tue, 18 Oct 2022 11:56:24 +0200 [thread overview]
Message-ID: <20221018095624.543287-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20221010045549.2221965-2-sgzhang@google.com>
On Mon, 2022-10-10 at 04:55:47 UTC, Ray Zhang wrote:
> To comply with latest kernel code requirement, change printk() to
> counterpart pr_ functions in mtdoops driver:
> - change printk(INFO) to pr_info()
> - change printk(DEBUG) to pr_debug()
> - change printk(WARNING) to pr_warn()
> - change printk(ERR) to pr_err()
>
> Note that only if dynamic debugging is enabled or DEBUG is defined,
> printk(KERN_DEBUG) and pr_debug() are equivalent; Otherwise pr_debug()
> is no-op, causing different behavior.
>
> Signed-off-by: Ray Zhang <sgzhang@google.com>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.
Miquel
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-10-18 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 4:55 [PATCH v4 0/3] mtd: mtdoops: use pr_ functions, add and direct call mtdoops_erase function when panic Ray Zhang
2022-10-10 4:55 ` [PATCH v4 1/3] mtd: mtdoops: change printk() to counterpart pr_ functions Ray Zhang
2022-10-18 9:56 ` Miquel Raynal [this message]
2022-10-10 4:55 ` [PATCH v4 2/3] mtd: mtdoops: add mtdoops_erase function and move mtdoops_inc_counter to after it Ray Zhang
2022-10-18 9:56 ` Miquel Raynal
2022-10-10 4:55 ` [PATCH v4 3/3] mtd: mtdoops: panic caused mtdoops to call mtdoops_erase function immediately Ray Zhang
2022-10-18 9:56 ` Miquel Raynal
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=20221018095624.543287-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=sgzhang@google.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).