On Tue, Dec 09, 2014 at 05:32:12PM +0100, Vincent Donnefort wrote: > On Tue, Dec 09, 2014 at 10:17:54AM -0500, Greg KH wrote: > > On Tue, Dec 09, 2014 at 10:56:04AM +0100, Vincent Donnefort wrote: > > > From: Todd Fujinaka <todd.fujinaka@xxxxxxxxx> > > > > > > Call igb_setup_link() when the PHY is powered up. > > > > > > Signed-off-by: Todd Fujinaka <todd.fujinaka@xxxxxxxxx> > > > Reported-by: Jeff Westfahl <jeff.westfahl@xxxxxx> > > > Tested-by: Aaron Brown <aaron.f.brown@xxxxxxxxx> > > > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx> > > > > > > diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c > > > index f145adb..5759a56 100644 > > > --- a/drivers/net/ethernet/intel/igb/igb_main.c > > > +++ b/drivers/net/ethernet/intel/igb/igb_main.c > > > @@ -1630,6 +1630,8 @@ void igb_power_up_link(struct igb_adapter *adapter) > > > igb_power_up_phy_copper(&adapter->hw); > > > else > > > igb_power_up_serdes_link_82575(&adapter->hw); > > > + > > > + igb_setup_link(&adapter->hw); > > > } > > > > > > /** > > > > What is the git commit id of this patch in Linus's tree, and what stable > > tree(s) do you want it applied to? > > Sorry for the oversight. > > The commit ID is aec653c43b0c55667355e26d7de1236bda9fb4e3 > > This patch has been introduced in linux 3.17. The bug has been > experienced on a intel device (Rangeley SOC) which needs > 3.9. > > It should so be applied to: > > 3.10 > 3.12 > 3.14 > Looks like it could also be applied to the 3.16 kernel as well. I'll queue it for the next release. Cheers, -- Luís > Vincent. > > > > > Please read Documentation/stable_kernel_rules.txt for how to properly > > let us know to include a patch. > > > > thanks, > > > > greg k-h > -- > To unsubscribe from this list: send the line "unsubscribe stable" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html