Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4 v2] irqchip: augment Gemini bindings to reflect Faraday origin
Date: Fri, 24 Mar 2017 09:29:28 +0000	[thread overview]
Message-ID: <604b75cd-e7ec-925d-e745-7ee7d45c602f@arm.com> (raw)
In-Reply-To: <20170318165326.20450-1-linus.walleij@linaro.org>

On 18/03/17 16:53, Linus Walleij wrote:
> When we merged the Gemini interrupt controller it was not yet
> discovered that this IP block is actually a standard Faraday
> Technology interrupt controller.
> 
> As the IP block will probably appear in other designs as well,
> let's augment the DT bindings to reflect that it is first and
> foremost a standard Faraday part with a function name (FTINTC010)
> so that people reusing the IP easily find the driver they need.
> 
> Sorry for the mistakes due to lack of information.
> 
> Cc: Greentime Hu <green.hu@gmail.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - No changes, just resending with the rest.

I've queued the series for 4.12.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

      parent reply	other threads:[~2017-03-24  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 16:53 [PATCH 1/4 v2] irqchip: augment Gemini bindings to reflect Faraday origin Linus Walleij
2017-03-18 16:53 ` [PATCH 2/4 v2] irqchip: refactor Gemini driver " Linus Walleij
2017-03-18 16:53 ` [PATCH 3/4 v2] irqchip: faraday: fix the trigger types Linus Walleij
2017-03-18 16:53 ` [PATCH 4/4 v2] irqchip: replace moxa with ftintc010 Linus Walleij
2017-03-19 10:21 ` [PATCH 1/4 v2] irqchip: augment Gemini bindings to reflect Faraday origin Hans Ulli Kroll
2017-03-24  9:29 ` 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=604b75cd-e7ec-925d-e745-7ee7d45c602f@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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