Re: [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-20 Thread David Miller
From: Andrew Goodbody Date: Wed, 20 Apr 2016 08:49:34 + > Sorry, I had no notification that this had happened. However I > thought that the plan was to revert v1 and go with David Rivshin's > patch instead. I'll see if I can create a revert in a little while.

Re: [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-20 Thread David Miller
From: Andrew Goodbody Date: Wed, 20 Apr 2016 08:49:34 + > Sorry, I had no notification that this had happened. However I > thought that the plan was to revert v1 and go with David Rivshin's > patch instead. I'll see if I can create a revert in a little while. Yes, that's fine.

RE: [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-20 Thread Andrew Goodbody
> -Original Message- > From: Andrew Goodbody > Date: Mon, 18 Apr 2016 14:53:25 +0100 > > > This is a fix for a NULL pointer dereference from cpsw which is > > triggered by having two slave PHYs attached to a cpsw network device. > > The problem is due to

RE: [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-20 Thread Andrew Goodbody
> -Original Message- > From: Andrew Goodbody > Date: Mon, 18 Apr 2016 14:53:25 +0100 > > > This is a fix for a NULL pointer dereference from cpsw which is > > triggered by having two slave PHYs attached to a cpsw network device. > > The problem is due to only maintaining a single

Re: [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-19 Thread David Miller
From: Andrew Goodbody Date: Mon, 18 Apr 2016 14:53:25 +0100 > This is a fix for a NULL pointer dereference from cpsw which is triggered > by having two slave PHYs attached to a cpsw network device. The problem is > due to only maintaining a single reference to a

Re: [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-19 Thread David Miller
From: Andrew Goodbody Date: Mon, 18 Apr 2016 14:53:25 +0100 > This is a fix for a NULL pointer dereference from cpsw which is triggered > by having two slave PHYs attached to a cpsw network device. The problem is > due to only maintaining a single reference to a PHY node in the prive data >

[PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-19 Thread Andrew Goodbody
Resend to add more people on Cc: as requested by Grygrii Strashko. This is a fix for a NULL pointer dereference from cpsw which is triggered by having two slave PHYs attached to a cpsw network device. The problem is due to only maintaining a single reference to a PHY node in the prive data which

[PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-19 Thread Andrew Goodbody
Resend to add more people on Cc: as requested by Grygrii Strashko. This is a fix for a NULL pointer dereference from cpsw which is triggered by having two slave PHYs attached to a cpsw network device. The problem is due to only maintaining a single reference to a PHY node in the prive data which

[PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-18 Thread Andrew Goodbody
This is a fix for a NULL pointer dereference from cpsw which is triggered by having two slave PHYs attached to a cpsw network device. The problem is due to only maintaining a single reference to a PHY node in the prive data which gets overwritten by the second PHY probe. So move the PHY node

[PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs

2016-04-18 Thread Andrew Goodbody
This is a fix for a NULL pointer dereference from cpsw which is triggered by having two slave PHYs attached to a cpsw network device. The problem is due to only maintaining a single reference to a PHY node in the prive data which gets overwritten by the second PHY probe. So move the PHY node