From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] crypto: marvell/cesa - forward devm_ioremap_resource() error code
Date: Thu, 17 Mar 2016 10:49:34 +0100 [thread overview]
Message-ID: <20160317104934.63e9e396@bbrezillon> (raw)
In-Reply-To: <1458208031-13463-2-git-send-email-boris.brezillon@free-electrons.com>
Sorry for the noise, just sent twice the same patch :-/.
Please ignore this one.
On Thu, 17 Mar 2016 10:47:11 +0100
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> Forward devm_ioremap_resource() error code instead of returning
> -ENOMEM.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Reported-by: Russell King - ARM Linux <linux@arm.linux.org.uk>
> Fixes: f63601fd616a ("crypto: marvell/cesa - add a new driver for Marvell's CESA")
> Cc: <stable@vger.kernel.org> # 4.2+
> ---
> drivers/crypto/marvell/cesa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/marvell/cesa.c b/drivers/crypto/marvell/cesa.c
> index c0656e7..80239ae 100644
> --- a/drivers/crypto/marvell/cesa.c
> +++ b/drivers/crypto/marvell/cesa.c
> @@ -420,7 +420,7 @@ static int mv_cesa_probe(struct platform_device *pdev)
> res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "regs");
> cesa->regs = devm_ioremap_resource(dev, res);
> if (IS_ERR(cesa->regs))
> - return -ENOMEM;
> + return PTR_ERR(cesa->regs);
>
> ret = mv_cesa_dev_dma_init(cesa);
> if (ret)
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-17 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 9:47 [PATCH] crypto: marvell/cesa - forward devm_ioremap_resource() error code Boris Brezillon
2016-03-17 9:47 ` Boris Brezillon
2016-03-17 9:49 ` Boris Brezillon [this message]
2016-03-17 11:13 ` Herbert Xu
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=20160317104934.63e9e396@bbrezillon \
--to=boris.brezillon@free-electrons.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