From: Marc Zyngier <maz@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Hector Martin <marcan@marcan.st>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
james.morse@arm.com, tglx@linutronix.de, will@kernel.org
Subject: Re: [PATCHv2 0/8] arm64: Support FIQ controller registration
Date: Mon, 08 Mar 2021 20:20:45 +0000 [thread overview]
Message-ID: <871rcps8gy.wl-maz@kernel.org> (raw)
In-Reply-To: <20210308175232.GA17002@C02TD0UTHF1T.local>
On Mon, 08 Mar 2021 17:52:32 +0000,
Mark Rutland <mark.rutland@arm.com> wrote:
>
> On Fri, Mar 05, 2021 at 07:08:50PM +0900, Hector Martin wrote:
> > On 02/03/2021 19.12, Mark Rutland wrote:
> > > I'm hoping that we can get the first 2 patches in as a preparatory cleanup for
> > > the next rc or so, and then the rest of the series can be rebased atop that.
> > > I've pushed the series out to my arm64/fiq branch [4] on kernel.org, also
> > > tagged as arm64-fiq-20210302, atop v5.12-rc1.
> >
> > Just a reminder to everyone that filesystems under v5.12-rc1 go explodey if
> > you use a swap file [1].
> >
> > I don't care for the M1 bring-up series (we don't *have* storage), but it's
> > worth pointing out for other people who might test this.
> >
> > Modulo that,
> >
> > Tested-by: Hector Martin <marcan@marcan.st>
> >
> > [1] https://lore.kernel.org/lkml/CAHk-=wjnzdLSP3oDxhf9eMTYo7GF-QjaNLBUH1Zk3c4A7X75YA@mail.gmail.com/
>
> Thanks!
>
> I've folded that in, with the series rebased to v5.12-rc2, tagged as
> arm64-fiq-20210308. I'm expecting that Marc will get the first couple of
> patches queued by rc4, so there's at least one rebase ahead.
Just pushed those two into -next, and planning to send them to tglx by
the end of the week.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-08 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 10:12 [PATCHv2 0/8] arm64: Support FIQ controller registration Mark Rutland
2021-03-02 10:12 ` [PATCHv2 1/8] ARM: ep93xx: Select GENERIC_IRQ_MULTI_HANDLER directly Mark Rutland
2021-03-02 10:12 ` [PATCHv2 2/8] irqchip: Do not blindly select CONFIG_GENERIC_IRQ_MULTI_HANDLER Mark Rutland
2021-03-02 10:12 ` [PATCHv2 3/8] genirq: Allow architectures to override set_handle_irq() fallback Mark Rutland
2021-03-02 10:12 ` [PATCHv2 4/8] arm64: don't use GENERIC_IRQ_MULTI_HANDLER Mark Rutland
2021-03-02 10:12 ` [PATCHv2 5/8] arm64: irq: rework root IRQ handler registration Mark Rutland
2021-03-02 10:12 ` [PATCHv2 6/8] arm64: entry: factor irq triage logic into macros Mark Rutland
2021-03-02 10:12 ` [PATCHv2 7/8] arm64: Always keep DAIF.[IF] in sync Mark Rutland
2021-03-02 10:12 ` [PATCHv2 8/8] arm64: irq: allow FIQs to be handled Mark Rutland
2021-03-05 10:08 ` [PATCHv2 0/8] arm64: Support FIQ controller registration Hector Martin
2021-03-08 17:52 ` Mark Rutland
2021-03-08 20:20 ` 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=871rcps8gy.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=will@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).