From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] irqchip/irq-mvebu-gicp: add missing spin_lock init
Date: Wed, 25 Oct 2017 09:37:03 +0200 [thread overview]
Message-ID: <87po9b4r1c.fsf@free-electrons.com> (raw)
In-Reply-To: <20171025072326.21030-1-antoine.tenart@free-electrons.com> (Antoine Tenart's message of "Wed, 25 Oct 2017 09:23:26 +0200")
Hi Antoine,
On mer., oct. 25 2017, Antoine Tenart <antoine.tenart@free-electrons.com> wrote:
> A spin lock is used in the irq-mvebu-gicp driver, but it is never
> initialized. This patch adds the missing spin_lock_init() call in the
> driver's probe function.
>
> Fixes: a68a63cb4dfc ("irqchip/irq-mvebu-gicp: Add new driver for Marvell GICP")
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
You could add the "Cc: stable at vger.kernel.org" flag so the previous
kernels can also benefit of this fix.
Besides this this patch looks obviously correct.
Reviewed-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
Gregory
> ---
> drivers/irqchip/irq-mvebu-gicp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/irqchip/irq-mvebu-gicp.c b/drivers/irqchip/irq-mvebu-gicp.c
> index b283fc90be1e..17a4a7b6cdbb 100644
> --- a/drivers/irqchip/irq-mvebu-gicp.c
> +++ b/drivers/irqchip/irq-mvebu-gicp.c
> @@ -194,6 +194,7 @@ static int mvebu_gicp_probe(struct platform_device *pdev)
> return -ENOMEM;
>
> gicp->dev = &pdev->dev;
> + spin_lock_init(&gicp->spi_lock);
>
> gicp->res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> if (!gicp->res)
> --
> 2.14.2
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-10-25 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 7:23 [PATCH] irqchip/irq-mvebu-gicp: add missing spin_lock init Antoine Tenart
2017-10-25 7:37 ` Gregory CLEMENT [this message]
2017-10-25 7:51 ` Marc Zyngier
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=87po9b4r1c.fsf@free-electrons.com \
--to=gregory.clement@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