From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Horman <horms@verge.net.au>
Date: Thu, 28 Nov 2013 06:45:56 +0000
Subject: Re: [PATCH 00/04] ARM: shmobile: Use SoC suffix for INTC compat string
Message-Id: <20131128064555.GA14878@verge.net.au>
List-Id: <linux-sh.vger.kernel.org>
References: <20131127231450.29081.98054.sendpatchset@w520>
In-Reply-To: <20131127231450.29081.98054.sendpatchset@w520>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-arm-kernel@lists.infradead.org

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"