From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Richard Fitzgerald <rf@opensource.cirrus.com>,
Lee Jones <lee.jones@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] irqchip updates for 4.20
Date: Sat, 06 Oct 2018 18:32:29 +0100 [thread overview]
Message-ID: <86sh1jt1zm.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1810061547480.5454@nanos.tec.linutronix.de>
Hi Thomas,
On Sat, 06 Oct 2018 14:53:01 +0100,
Thomas Gleixner <tglx@linutronix.de> wrote:
>
> Marc,
>
> On Fri, 5 Oct 2018, Marc Zyngier wrote:
> > Here's the set of irqchip updates for 4.20. On the menu this time,
> > support for the Marvell SEI and Cirrus Logic Madera interrupt
> > controllers, support for kexec on GICv3 system, as well as a few
> > fixes and cleanups.
> >
> > Note that the GICv3/kexec stuff depends on some EFI updates. The whole
> > branch is thus based on tip/efi/irqchip which Ingo has created for
> > this purpose.
> >
> > Please pull,
>
> Done, but
>
> > Richard Fitzgerald (1):
> > irqchip: Add driver for Cirrus Logic Madera codecs
>
> This one breaks the build because MADERA_IRQ is selected by MFD_MADERA, but
> the updates to the header file are not yet upstream. It works against next
> but not standalone. Breaks allyes/allmod/randconfig builds
Really sorry about that, I should have tested it more carefully before
queuing it.
> So this commit needs to go through MFD along with the other related
> changes. I zapped it from irq/core already.
Good call. Thanks for taking care of it, and sorry again for the mess.
M.
--
Jazz is not dead, it just smell funny.
prev parent reply other threads:[~2018-10-06 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 11:29 Marc Zyngier
2018-10-06 13:53 ` Thomas Gleixner
2018-10-06 17:32 ` Marc Zyngier [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=86sh1jt1zm.wl-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rf@opensource.cirrus.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®