From: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
To: Marek Vasut <marek.vasut@gmail.com>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>
Cc: ldv-project@linuxtesting.org,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: spi-nor: hisi: do not ignore clk_prepare_enable() failure
Date: Tue, 7 Mar 2017 21:57:14 +0100 [thread overview]
Message-ID: <483ebb87-1b22-be6a-780d-66b73cdaff72@wedev4u.fr> (raw)
In-Reply-To: <0066fec2-492a-52de-3c2e-ebce4b9f452a@gmail.com>
Le 18/02/2017 à 16:23, Marek Vasut a écrit :
> On 02/17/2017 11:08 PM, Alexey Khoroshilov wrote:
>> hisi_spi_nor_probe() ignores clk_prepare_enable() error code.
>> The patch fixes that.
>>
>> Found by Linux Driver Verification project (linuxtesting.org).
>>
>> Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
>
> Acked-by: Marek Vasut <marek.vasut@gmail.com>
>
Applied to spi-nor/next
Thanks!
>> ---
>> drivers/mtd/spi-nor/hisi-sfc.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/spi-nor/hisi-sfc.c b/drivers/mtd/spi-nor/hisi-sfc.c
>> index 20378b0d55e9..a286350627a6 100644
>> --- a/drivers/mtd/spi-nor/hisi-sfc.c
>> +++ b/drivers/mtd/spi-nor/hisi-sfc.c
>> @@ -448,8 +448,11 @@ static int hisi_spi_nor_probe(struct platform_device *pdev)
>> if (!host->buffer)
>> return -ENOMEM;
>>
>> + ret = clk_prepare_enable(host->clk);
>> + if (ret)
>> + return ret;
>> +
>> mutex_init(&host->lock);
>> - clk_prepare_enable(host->clk);
>> hisi_spi_nor_init(host);
>> ret = hisi_spi_nor_register_all(host);
>> if (ret)
>>
>
>
prev parent reply other threads:[~2017-03-08 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:08 Alexey Khoroshilov
2017-02-18 15:23 ` Marek Vasut
2017-03-07 20:57 ` Cyrille Pitchen [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=483ebb87-1b22-be6a-780d-66b73cdaff72@wedev4u.fr \
--to=cyrille.pitchen@wedev4u.fr \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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
all inboxes | Powered by JetHome®