linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] ARM: shmobile: BOCK-W: change Ether device name
@ 2013-06-17 19:39 Sergei Shtylyov
  2013-06-18  7:23 ` Simon Horman
  0 siblings, 1 reply; 2+ messages in thread
From: Sergei Shtylyov @ 2013-06-17 19:39 UTC (permalink / raw)
  To: linux-arm-kernel

When changing the name of Ether platform device in the commit c02f846938fe (ARM:
shmobile: r8a7778: fix Ether device name), I completely forgot that there's also
platform  device name used in bockw_pinctrl_map[], so the commit "ARM: shmobile:
BOCK-W: add Ether support" went in with the old "sh-eth" device name. Now change
it to "r8a777x-ether" in accordance with the commits that are now in  the  'net-
next.git' repository,  otherwise BOCK-W Ether support won't work in 3.11.

Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

---
This patch is atop of Simon's 'renesas.git' repo, 'renesas-next-20130617v3' tag.

 arch/arm/mach-shmobile/board-bockw.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: renesas/arch/arm/mach-shmobile/board-bockw.c
===================================================================
--- renesas.orig/arch/arm/mach-shmobile/board-bockw.c
+++ renesas/arch/arm/mach-shmobile/board-bockw.c
@@ -144,7 +144,7 @@ static struct rcar_phy_platform_data usb
 
 static const struct pinctrl_map bockw_pinctrl_map[] = {
 	/* Ether */
-	PIN_MAP_MUX_GROUP_DEFAULT("sh-eth", "pfc-r8a7778",
+	PIN_MAP_MUX_GROUP_DEFAULT("r8a777x-ether", "pfc-r8a7778",
 				  "ether_rmii", "ether"),
 	/* HSPI0 */
 	PIN_MAP_MUX_GROUP_DEFAULT("sh-hspi.0", "pfc-r8a7778",

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [PATCH] ARM: shmobile: BOCK-W: change Ether device name
  2013-06-17 19:39 [PATCH] ARM: shmobile: BOCK-W: change Ether device name Sergei Shtylyov
@ 2013-06-18  7:23 ` Simon Horman
  0 siblings, 0 replies; 2+ messages in thread
From: Simon Horman @ 2013-06-18  7:23 UTC (permalink / raw)
  To: linux-arm-kernel

On Mon, Jun 17, 2013 at 11:39:44PM +0400, Sergei Shtylyov wrote:
> When changing the name of Ether platform device in the commit c02f846938fe (ARM:
> shmobile: r8a7778: fix Ether device name), I completely forgot that there's also
> platform  device name used in bockw_pinctrl_map[], so the commit "ARM: shmobile:
> BOCK-W: add Ether support" went in with the old "sh-eth" device name. Now change
> it to "r8a777x-ether" in accordance with the commits that are now in  the  'net-
> next.git' repository,  otherwise BOCK-W Ether support won't work in 3.11.
> 
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> 
> ---
> This patch is atop of Simon's 'renesas.git' repo, 'renesas-next-20130617v3' tag.

Thanks, I have queued-this up in the boards branch.

> 
>  arch/arm/mach-shmobile/board-bockw.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: renesas/arch/arm/mach-shmobile/board-bockw.c
> ===================================================================
> --- renesas.orig/arch/arm/mach-shmobile/board-bockw.c
> +++ renesas/arch/arm/mach-shmobile/board-bockw.c
> @@ -144,7 +144,7 @@ static struct rcar_phy_platform_data usb
>  
>  static const struct pinctrl_map bockw_pinctrl_map[] = {
>  	/* Ether */
> -	PIN_MAP_MUX_GROUP_DEFAULT("sh-eth", "pfc-r8a7778",
> +	PIN_MAP_MUX_GROUP_DEFAULT("r8a777x-ether", "pfc-r8a7778",
>  				  "ether_rmii", "ether"),
>  	/* HSPI0 */
>  	PIN_MAP_MUX_GROUP_DEFAULT("sh-hspi.0", "pfc-r8a7778",
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-06-18  7:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-17 19:39 [PATCH] ARM: shmobile: BOCK-W: change Ether device name Sergei Shtylyov
2013-06-18  7:23 ` Simon Horman

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).