From: Marc Zyngier <marc.zyngier@arm.com>
To: "Shenhar, Talel" <talel@amazon.com>, Rob Herring <robh@kernel.org>
Cc: nicolas.ferre@microchip.com, jason@lakedaemon.net,
mark.rutland@arm.com, mchehab+samsung@kernel.org,
davem@davemloft.net, shawn.lin@rock-chips.com,
tglx@linutronix.de, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
dwmw@amazon.co.uk, benh@kernel.crashing.org, jonnyc@amazon.com,
hhhawa@amazon.com, ronenk@amazon.com, hanochu@amazon.com,
barakw@amazon.com
Subject: Re: [PATCH v4 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC
Date: Tue, 9 Jul 2019 09:15:21 +0100 [thread overview]
Message-ID: <ff3794af-cd5a-5331-fca0-30280530670e@arm.com> (raw)
In-Reply-To: <f1fd393d-0b8c-16f1-9ac2-0589e9cb9ea7@amazon.com>
On 09/07/2019 06:59, Shenhar, Talel wrote:
> Marc, should I publish those fixes as new patch that updates the
> dt-bindings or new patchset to this list?
If you are going to update the binding, please submit a patch on top of
mainline, as it's been merged already.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2019-07-09 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:34 [PATCH v4 0/2] Amazon's Annapurna Labs Fabric Interrupt Controller Talel Shenhar
2019-06-10 8:34 ` [PATCH v4 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC Talel Shenhar
2019-06-18 10:46 ` Marc Zyngier
2019-07-09 2:23 ` Rob Herring
2019-07-09 5:59 ` Shenhar, Talel
2019-07-09 8:15 ` Marc Zyngier [this message]
2019-07-09 8:17 ` Shenhar, Talel
2019-07-09 13:25 ` Rob Herring
2019-06-10 8:34 ` [PATCH v4 2/2] irqchip: al-fic: Introduce Amazon's Annapurna Labs Fabric Interrupt Controller Driver Talel Shenhar
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=ff3794af-cd5a-5331-fca0-30280530670e@arm.com \
--to=marc.zyngier@arm.com \
--cc=barakw@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=jason@lakedaemon.net \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=ronenk@amazon.com \
--cc=shawn.lin@rock-chips.com \
--cc=talel@amazon.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®