From: Marc Zyngier <maz@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Salter <msalter@redhat.com>,
Robert Richter <rrichter@marvell.com>,
Tim Harvey <tharvey@gateworks.com>,
Jason Cooper <jason@lakedaemon.net>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] irqchip fixes for 5.6, take #2
Date: Sun, 15 Mar 2020 10:13:38 +0000 [thread overview]
Message-ID: <76dcc2d8532f8e3a87bf03469b9c2c19@kernel.org> (raw)
In-Reply-To: <20200315084846.h222n5pf4jvpojec@wunner.de>
Lukas,
On 2020-03-15 08:48, Lukas Wunner wrote:
> On Sat, Mar 14, 2020 at 10:30:00AM +0000, Marc Zyngier wrote:
>> This is hopefully the last irqchip update for 5.6. This time, a single
>> patch working around a hardware issue on the Cavium ThunderX and its
>> derivatives.
>
> Hm, I was hoping to see the BCM2835 irqchip fix in this pull:
>
> https://lore.kernel.org/lkml/f97868ba4e9b86ddad71f44ec9d8b3b7d8daa1ea.1582618537.git.lukas@wunner.de/
>
> That patch fixes a pretty grave issue so I'd be really grateful
> if anyone could pick it up (or provide feedback why it can't be
> picked up just yet).
Whilst I don't dispute that this patch addresses a serious issue,
it is in no way an urgent fix -- the issue is already 7.5 year old,
so a couple of week delay isn't going to change the world. Also,
the system does work without this fix, so I'm quite confident
leaving it for 5.7.
But thanks for this email anyway, as it reminded me that although
I had picked that patch for 5.7, I didn't apply it just yet. This
is now fixed, and the patch should be picked up by -next shortly.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-03-15 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 10:30 [GIT PULL] irqchip fixes for 5.6, take #2 Marc Zyngier
2020-03-15 8:48 ` Lukas Wunner
2020-03-15 10:13 ` Marc Zyngier [this message]
2020-03-15 11:21 ` Lukas Wunner
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=76dcc2d8532f8e3a87bf03469b9c2c19@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=msalter@redhat.com \
--cc=rrichter@marvell.com \
--cc=tglx@linutronix.de \
--cc=tharvey@gateworks.com \
/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).