From: Lukas Wunner <lukas@wunner.de>
To: Marc Zyngier <maz@kernel.org>
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 12:21:21 +0100 [thread overview]
Message-ID: <20200315112121.n5mucfsibs2eeudg@wunner.de> (raw)
In-Reply-To: <76dcc2d8532f8e3a87bf03469b9c2c19@kernel.org>
On Sun, Mar 15, 2020 at 10:13:38AM +0000, Marc Zyngier wrote:
> On 2020-03-15 08:48, Lukas Wunner wrote:
> > Hm, I was hoping to see the BCM2835 irqchip fix in this pull:
> >
> > https://lore.kernel.org/lkml/f97868ba4e9b86ddad71f44ec9d8b3b7d8daa1ea.1582618537.git.lukas@wunner.de/
>
> 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.
Sure, fair enough, thanks.
Bonne fin de week-end,
Lukas
prev parent reply other threads:[~2020-03-15 11:21 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
2020-03-15 11:21 ` Lukas Wunner [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=20200315112121.n5mucfsibs2eeudg@wunner.de \
--to=lukas@wunner.de \
--cc=catalin.marinas@arm.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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).