From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
marek.vasut@gmail.com, cyrille.pitchen@wedev4u.fr,
narmstrong@baylibre.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Handle clk_prepare_enable/clk_disable_unprepare.
Date: Fri, 4 Aug 2017 09:31:23 +0200 [thread overview]
Message-ID: <20170804093123.48e49db1@bbrezillon> (raw)
In-Reply-To: <1501587309-20900-1-git-send-email-arvind.yadav.cs@gmail.com>
On Tue, 1 Aug 2017 17:05:08 +0530
Arvind Yadav <arvind.yadav.cs@gmail.com> wrote:
> clk_prepare_enable() can fail here and we must check its return value.
> *_probe() can fail here and we must disable clock.
>
> Arvind Yadav (6):
> [PATCH 1/6] mtd: nand: denali: Handle return value of clk_prepare_enable.
> [PATCH 2/6] mtd: oxnas_nand: Handle clk_prepare_enable/clk_disable_unprepare.
> [PATCH 3/6] mtd: nand: lpc32xx_slc: Handle return value of clk_prepare_enable.
> [PATCH 4/6] mtd: nand: vf610_nfc: Handle return value of clk_prepare_enable.
> [PATCH 5/6] mtd: nand: lpc32xx_mlc: Handle return value of clk_prepare_enable.
> [PATCH 6/6] mtd: st_spi_fsm: Handle clk_prepare_enable/clk_disable_unprepare.
Applied everything except patch 4.
Thanks,
Boris
>
> drivers/mtd/devices/st_spi_fsm.c | 20 ++++++++++++--------
> drivers/mtd/nand/denali_dt.c | 4 +++-
> drivers/mtd/nand/lpc32xx_mlc.c | 9 +++++++--
> drivers/mtd/nand/lpc32xx_slc.c | 9 +++++++--
> drivers/mtd/nand/oxnas_nand.c | 25 ++++++++++++++++++-------
> drivers/mtd/nand/vf610_nfc.c | 5 ++++-
> 6 files changed, 51 insertions(+), 21 deletions(-)
>
prev parent reply other threads:[~2017-08-04 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 11:35 [PATCH 0/6] Handle clk_prepare_enable/clk_disable_unprepare Arvind Yadav
2017-08-01 11:35 ` [PATCH 1/6] mtd: nand: denali: Handle return value of clk_prepare_enable Arvind Yadav
2017-08-04 7:31 ` Boris Brezillon [this message]
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=20170804093123.48e49db1@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=narmstrong@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox