From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Marc Zyngier <maz@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Kurt Kanzenbach <kurt@linutronix.de>,
Vladimir Oltean <olteanv@gmail.com>
Subject: Re: [PATCH v7 0/2] Add support for Layerscape external interrupt lines
Date: Tue, 12 Nov 2019 12:44:42 +0100 [thread overview]
Message-ID: <02f7a8ad-be85-b43a-be36-988d96ced056@rasmusvillemoes.dk> (raw)
In-Reply-To: <8e1877ab5a1fecace3b2383789bdf404@www.loen.fr>
On 12/11/2019 11.58, Marc Zyngier wrote:
> On 2019-11-12 11:27, Rasmus Villemoes wrote:
>> On 11/11/2019 11.24, Marc Zyngier wrote:
>>> Applied to irqchip-next.
>>
>> Thanks! Can I assume that branch doesn't get rebased so 87cd38dfd9e6 is
>> a stable SHA1? I want to send a patch adding the node to ls1021a.dtsi,
>> and I hope not to have to wait another release cycle.
>
> I usually try to avoid rebasing it, unless something really bad shows up.
>
> Now, just adding a node to a DT shouldn't break anything, right? You
> should be able to do that change and get things working magically once
> this code hits mainline.
Well, yes, but I wanted to refer to the binding documentation in the
form of a reference to that SHA1. But I suppose I can just do that in
the cover letter or below ---.
Thanks,
Rasmus
prev parent reply other threads:[~2019-11-12 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 12:21 [PATCH v7 0/2] Add support for Layerscape external interrupt lines Rasmus Villemoes
2019-11-07 12:21 ` [PATCH v7 1/2] dt/bindings: Add bindings for Layerscape external irqs Rasmus Villemoes
2019-11-20 13:21 ` [tip: irq/core] " tip-bot2 for Rasmus Villemoes
2019-11-07 12:21 ` [PATCH v7 2/2] irqchip: add support for Layerscape external interrupt lines Rasmus Villemoes
2019-11-20 13:21 ` [tip: irq/core] irqchip: Add " tip-bot2 for Rasmus Villemoes
2019-11-11 10:24 ` [PATCH v7 0/2] " Marc Zyngier
2019-11-11 10:31 ` Vladimir Oltean
2019-11-12 10:18 ` Rasmus Villemoes
2019-11-12 10:58 ` Marc Zyngier
2019-11-12 11:44 ` Rasmus Villemoes [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=02f7a8ad-be85-b43a-be36-988d96ced056@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=olteanv@gmail.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).