From: Ray Zhang <sgzhang@google.com>
To: 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,
Ray Zhang <sgzhang@google.com>
Subject: [PATCH v3 0/3] mtd: mtdoops: use pr_ functions, add and direct call mtdoops_erase function when panic
Date: Fri, 7 Oct 2022 21:50:24 +0000 [thread overview]
Message-ID: <20221007215027.918507-1-sgzhang@google.com> (raw)
In mtdoops driver, to comply with latest kernel code requirement, change
printk() to counterpart pr_ functions. [Note: change to pr_debug() may
cause behavior difference.] Add mtdoops_erase function; When panic
function invokes mtdoops, if needed, call mtdoops_erase function
immediately.
Ray Zhang (3):
mtd: mtdoops: change printk() to counterpart pr_ functions
mtd: mtdoops: add mtdoops_erase function and move mtdoops_inc_counter
to after it
mtd: mtdoops: panic caused mtdoops to call mtdoops_erase function
immediately
drivers/mtd/mtdoops.c | 107 +++++++++++++++++++++++-------------------
1 file changed, 60 insertions(+), 47 deletions(-)
--
2.38.0.rc1.362.ged0d419d3c-goog
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2022-10-07 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 21:50 Ray Zhang [this message]
2022-10-07 21:50 ` [PATCH v3 1/3] mtd: mtdoops: change printk() to counterpart pr_ functions Ray Zhang
2022-10-08 7:25 ` Joe Perches
2022-10-09 10:17 ` Miquel Raynal
2022-10-07 21:50 ` [PATCH v3 2/3] mtd: mtdoops: add mtdoops_erase function and move mtdoops_inc_counter to after it Ray Zhang
2022-10-07 21:50 ` [PATCH v3 3/3] mtd: mtdoops: panic caused mtdoops to call mtdoops_erase function immediately Ray Zhang
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=20221007215027.918507-1-sgzhang@google.com \
--to=sgzhang@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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