From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/04] ARM: shmobile: Use SoC suffix for INTC compat string
Date: Thu, 28 Nov 2013 06:45:56 +0000 [thread overview]
Message-ID: <20131128064555.GA14878@verge.net.au> (raw)
In-Reply-To: <20131127231450.29081.98054.sendpatchset@w520>
On Thu, Nov 28, 2013 at 08:14:50AM +0900, Magnus Damm wrote:
> ARM: shmobile: Use SoC suffix for INTC compat string
>
> [PATCH 01/04] ARM: shmobile: Use sh73a0 suffix for INTC compat string
> [PATCH 02/04] ARM: shmobile: Use r8a7740 suffix for INTC compat string
> [PATCH 03/04] ARM: shmobile: Use r8a7778 suffix for INTC compat string
> [PATCH 04/04] ARM: shmobile: Use r8a7779 suffix for INTC compat string
>
> Update the DTS for INTC irqpin devices to include the SoC in the compat string.
>
> Both IRQC and INTC irqpin need documentation for the DT bindings, and this
> will happen in incremental patches.
I have posted some patches for that a few moments ago :)
I am curious to if it is intentional that this series replaces
the use of less-specific compat strings with more specific ones
while the recent update to the r8a7790 supplemented the
less-specific renesas,irqc comat string with the more-specific
renesas,irqc-r8a7790 compat string.
i.e.
before: "renesas,intc-irqpin"
after: "renesas,intc-irqpin-sh73a0"
as opposed to
before: "renesas,irqc"
after: "renesas,irqc-r8a7790", "renesas,irqc"
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/04] ARM: shmobile: Use SoC suffix for INTC compat string
Date: Thu, 28 Nov 2013 15:45:56 +0900 [thread overview]
Message-ID: <20131128064555.GA14878@verge.net.au> (raw)
In-Reply-To: <20131127231450.29081.98054.sendpatchset@w520>
On Thu, Nov 28, 2013 at 08:14:50AM +0900, Magnus Damm wrote:
> ARM: shmobile: Use SoC suffix for INTC compat string
>
> [PATCH 01/04] ARM: shmobile: Use sh73a0 suffix for INTC compat string
> [PATCH 02/04] ARM: shmobile: Use r8a7740 suffix for INTC compat string
> [PATCH 03/04] ARM: shmobile: Use r8a7778 suffix for INTC compat string
> [PATCH 04/04] ARM: shmobile: Use r8a7779 suffix for INTC compat string
>
> Update the DTS for INTC irqpin devices to include the SoC in the compat string.
>
> Both IRQC and INTC irqpin need documentation for the DT bindings, and this
> will happen in incremental patches.
I have posted some patches for that a few moments ago :)
I am curious to if it is intentional that this series replaces
the use of less-specific compat strings with more specific ones
while the recent update to the r8a7790 supplemented the
less-specific renesas,irqc comat string with the more-specific
renesas,irqc-r8a7790 compat string.
i.e.
before: "renesas,intc-irqpin"
after: "renesas,intc-irqpin-sh73a0"
as opposed to
before: "renesas,irqc"
after: "renesas,irqc-r8a7790", "renesas,irqc"
next prev parent reply other threads:[~2013-11-28 6:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 23:14 [PATCH 00/04] ARM: shmobile: Use SoC suffix for INTC compat string Magnus Damm
2013-11-27 23:14 ` Magnus Damm
2013-11-27 23:14 ` [PATCH 01/04] ARM: shmobile: Use sh73a0 " Magnus Damm
2013-11-27 23:14 ` Magnus Damm
2013-11-27 23:15 ` [PATCH 02/04] ARM: shmobile: Use r8a7740 " Magnus Damm
2013-11-27 23:15 ` Magnus Damm
2013-11-27 23:15 ` [PATCH 03/04] ARM: shmobile: Use r8a7778 " Magnus Damm
2013-11-27 23:15 ` Magnus Damm
2013-11-27 23:15 ` [PATCH 04/04] ARM: shmobile: Use r8a7779 " Magnus Damm
2013-11-27 23:15 ` Magnus Damm
2013-11-28 6:45 ` Simon Horman [this message]
2013-11-28 6:45 ` [PATCH 00/04] ARM: shmobile: Use SoC " Simon Horman
2013-12-04 19:21 ` Magnus Damm
2013-12-04 19:21 ` Magnus Damm
2013-12-05 2:50 ` Simon Horman
2013-12-05 2:50 ` Simon Horman
2013-12-05 5:17 ` Simon Horman
2013-12-05 5:17 ` Simon Horman
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=20131128064555.GA14878@verge.net.au \
--to=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.