Message ID | 1414002412-13615-3-git-send-email-sebastian.hesselbarth@gmail.com |
---|---|
State | New |
Headers | show |
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Date: Sat, 25 Oct 2014 12:08:59 +0200 > Do not add phy include to the board file but platform_data include > instead. > > Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> > --- > David, > > I should have compile tested this patch earlier. I did now on > pxa168_defconfig right after I received an 0-day kbuild error > on this patch. > > This is the corresponding fix, can you please squash it in? > > Thanks and sorry for the noise, Patch applied to net-next, but: 1) There is never any way for me to "squash" a patch into an old one. Once I apply a patch it is a permanent commit in my tree and cannot be undone and/or modified. Therefore the only thing you can do is send me a relative fix and that's what shows up in my tree as yet another later commit. 2) Always be specific about the target tree in you subject, line. Never assume I can figure it out by context. Thanks.
On 28.10.2014 21:49, David Miller wrote: > From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> > Date: Sat, 25 Oct 2014 12:08:59 +0200 > >> Do not add phy include to the board file but platform_data include >> instead. >> >> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> >> --- >> David, >> >> I should have compile tested this patch earlier. I did now on >> pxa168_defconfig right after I received an 0-day kbuild error >> on this patch. >> >> This is the corresponding fix, can you please squash it in? >> >> Thanks and sorry for the noise, > > Patch applied to net-next, but: > > 1) There is never any way for me to "squash" a patch into an old > one. Once I apply a patch it is a permanent commit in my tree > and cannot be undone and/or modified. > > Therefore the only thing you can do is send me a relative fix > and that's what shows up in my tree as yet another later commit. Ok, good to know and sorry for the crippled fixup patch. I was assuming that net-next is also rebased until pulled/moved to some stable state. > 2) Always be specific about the target tree in you subject, > line. Never assume I can figure it out by context. Also, sorry for the little information given. Thanks, Sebastian
diff --git a/arch/arm/mach-mmp/gplugd.c b/arch/arm/mach-mmp/gplugd.c index d81b2475e67e..3b5794cd0357 100644 --- a/arch/arm/mach-mmp/gplugd.c +++ b/arch/arm/mach-mmp/gplugd.c @@ -12,6 +12,7 @@ #include <linux/platform_device.h> #include <linux/gpio.h> #include <linux/gpio-pxa.h> +#include <linux/phy.h> #include <asm/mach/arch.h> #include <asm/mach-types.h> @@ -158,6 +159,7 @@ struct pxa168_eth_platform_data gplugd_eth_platform_data = { .port_number = 0, .phy_addr = 0, .speed = 0, /* Autonagotiation */ + .intf = PHY_INTERFACE_MODE_RMII, .init = gplugd_eth_init, }; diff --git a/include/linux/pxa168_eth.h b/include/linux/pxa168_eth.h index 18d75e795606..37c381120bc8 100644 --- a/include/linux/pxa168_eth.h +++ b/include/linux/pxa168_eth.h @@ -13,6 +13,7 @@ struct pxa168_eth_platform_data { */ int speed; /* 0, SPEED_10, SPEED_100 */ int duplex; /* DUPLEX_HALF or DUPLEX_FULL */ + phy_interface_t intf; /* * Override default RX/TX queue sizes if nonzero.