From: miquel.raynal@bootlin.com (Miquel Raynal)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] mtd: nand: Remove print after allocation failure
Date: Mon, 19 Mar 2018 23:47:29 +0100 [thread overview]
Message-ID: <20180319234729.73fb800d@xps13> (raw)
In-Reply-To: <1521390796-13715-2-git-send-email-arushisinghal19971997@gmail.com>
Hi Arushi,
On Sun, 18 Mar 2018 22:03:16 +0530, Arushi Singhal
<arushisinghal19971997@gmail.com> wrote:
> The prints after [k|v][m|z|c]alloc() etc. functions are not needed, because
> in case of failure, allocator will print their internal error prints
> anyway.
>
> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
> ---
> changes in v2
> *done the similar changes in other files.
>
> drivers/mtd/nand/ams-delta.c | 1 -
> drivers/mtd/nand/atmel/nand-controller.c | 13 +++---------
> drivers/mtd/nand/marvell_nand.c | 8 ++------
> drivers/mtd/nand/nandsim.c | 35 ++++++++------------------------
> drivers/mtd/nand/ndfc.c | 4 +---
> drivers/mtd/nand/sunxi_nand.c | 4 +---
> 6 files changed, 15 insertions(+), 50 deletions(-)
>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miqu?l
--
Miquel Raynal, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-19 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 16:33 [PATCH v2 1/2] mtd: maps: Remove print after allocation failure Arushi Singhal
2018-03-18 16:33 ` [PATCH v2 2/2] mtd: nand: " Arushi Singhal
2018-03-19 22:47 ` Miquel Raynal [this message]
2018-03-19 22:42 ` [PATCH v2 1/2] mtd: maps: " Miquel Raynal
-- strict thread matches above, loose matches on Subject: below --
2018-03-20 15:31 Arushi Singhal
2018-03-20 15:31 ` [PATCH v2 2/2] mtd: nand: " Arushi Singhal
2018-03-20 16:21 ` Nicolas Ferre
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=20180319234729.73fb800d@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).