From: Marc Zyngier <marc.zyngier@arm.com>
To: Fabio Estevam <festevam@gmail.com>, stable@vger.kernel.org
Cc: Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH v2] irqchip/gic: Allow self-SGIs for SMP on UP configurations
Date: Fri, 9 Sep 2016 15:40:49 +0100 [thread overview]
Message-ID: <57D2C9F1.5070900@arm.com> (raw)
In-Reply-To: <1473428682-14552-1-git-send-email-festevam@gmail.com>
Hi Fabio,
On 09/09/16 14:44, Fabio Estevam wrote:
> From: Marc Zyngier <marc.zyngier@arm.com>
>
> commit 059e232089e45b0befc9933d31209c225e08b426 upstream.
>
> On systems where a single CPU is present, the GIC may not support
> having SGIs delivered to a target list. In that case, we use the
> self-SGI mechanism to allow the interrupt to be delivered locally.
>
> Cc: <stable@vger.kernel.org> # 4.7.x
> Tested-by: Fabio Estevam <fabio.estevam@nxp.com>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
I'm sorry, but what is the justification for this to be backported to a
stable kernel? It is not a regression, since we never supported this
kind of HW before. This is not a workaround for an erratum either.
If that was a kernel bug, why not backport it all the way the the oldest
stable, instead of limiting it to v4.7?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-09-09 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 13:44 [PATCH v2] irqchip/gic: Allow self-SGIs for SMP on UP configurations Fabio Estevam
2016-09-09 14:40 ` Marc Zyngier [this message]
2016-09-09 15:31 ` Fabio Estevam
2016-09-09 15:42 ` Marc Zyngier
2016-09-09 15:48 ` Fabio Estevam
2016-09-09 16:06 ` Marc Zyngier
2016-09-09 16:12 ` Greg KH
2016-09-09 16:10 ` Greg KH
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=57D2C9F1.5070900@arm.com \
--to=marc.zyngier@arm.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=stable@vger.kernel.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).