From: Andrew Lunn
Date: Thu, 13 Oct 2016 18:29:01 +0200
> Just for my clarification:
>
> We are in the middle of the merge window. What does net-next and net
> mean at the moment?
Once I merge net-next to Linus, bug fixes should go to 'net'.
And for the past day or so I've been slowly merging
> On Thu, Oct 13, 2016 at 12:04:38PM -0400, David Miller wrote:
> From: Andrew Lunn
> Date: Wed, 12 Oct 2016 22:14:53 +0200
>
> > The phy_start() is used to indicate the PHY is now ready to do its
> > work. The state is changed, normally to PHY_UP which means that both
> > the MAC and the PHY are
From: Andrew Lunn
Date: Wed, 12 Oct 2016 22:14:53 +0200
> The phy_start() is used to indicate the PHY is now ready to do its
> work. The state is changed, normally to PHY_UP which means that both
> the MAC and the PHY are ready.
>
> If the phy driver is using polling, when the next poll happens,
On Wed, Oct 12, 2016 at 10:14:53PM +0200, Andrew Lunn wrote:
> The phy_start() is used to indicate the PHY is now ready to do its
> work. The state is changed, normally to PHY_UP which means that both
> the MAC and the PHY are ready.
>
> If the phy driver is using polling, when the next poll happe
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
a
