From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: linux-kernel@vger.kernel.org
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Joe Perches <joe@perches.com>
Subject: [PATCH v2 0/3] mtd: lpddr: Fix bad logic bug in print_drs_error
Date: Mon, 27 Apr 2020 14:48:58 -0500 [thread overview]
Message-ID: <cover.1588016644.git.gustavo@embeddedor.com> (raw)
Hi,
This series aims to fix a bad logic bug in print_drs_error, which is
tagged for -stable. The series also include some formatting fixups.
Thanks
Changes in v2:
- Coalesce formats in Patch 2.
- Remove inline from print_drs_error in Patch 3.
- Update changelog texts according to the last
changes.
Gustavo A. R. Silva (3):
mtd: lpddr: Fix bad logic in print_drs_error
mtd: lpddr: Replace printk with pr_notice
mtd: lpddr: Move function print_drs_error to lpddr_cmds.c
drivers/mtd/lpddr/lpddr_cmds.c | 28 ++++++++++++++++++++++++++++
include/linux/mtd/pfow.h | 33 ---------------------------------
2 files changed, 28 insertions(+), 33 deletions(-)
--
2.26.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-04-27 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 19:48 Gustavo A. R. Silva [this message]
2020-04-27 19:50 ` [PATCH v2 1/3] mtd: lpddr: Fix bad logic in print_drs_error Gustavo A. R. Silva
2020-04-27 20:08 ` Miquel Raynal
2020-05-19 16:22 ` Gustavo A. R. Silva
2020-09-07 7:34 ` Miquel Raynal
2020-04-27 19:54 ` [PATCH v2 2/3] mtd: lpddr: Replace printk with pr_notice Gustavo A. R. Silva
2020-04-27 20:09 ` Miquel Raynal
2020-09-07 7:34 ` Miquel Raynal
2020-04-27 19:56 ` [PATCH v2 3/3] mtd: lpddr: Move function print_drs_error to lpddr_cmds.c Gustavo A. R. Silva
2020-04-27 20:09 ` Miquel Raynal
2020-09-07 7:34 ` 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=cover.1588016644.git.gustavo@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=joe@perches.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;
as well as URLs for NNTP newsgroup(s).