On Thursday, April 19, 2018 09:34 AM, Chris Ruehl wrote:
On Thursday, April 19, 2018 09:21 AM, Chris Ruehl wrote:
On Wednesday, April 18, 2018 09:02 PM, Andrew Lunn wrote:
On Wed, Apr 18, 2018 at 02:56:01PM +0200, Andrew Lunn wrote:
On Wed, Apr 18, 2018 at 09:34:16AM +0800, Chris Ruehl
On Thursday, April 19, 2018 09:21 AM, Chris Ruehl wrote:
On Wednesday, April 18, 2018 09:02 PM, Andrew Lunn wrote:
On Wed, Apr 18, 2018 at 02:56:01PM +0200, Andrew Lunn wrote:
On Wed, Apr 18, 2018 at 09:34:16AM +0800, Chris Ruehl wrote:
Hello,
I like to get your heads up at a regression
On Wednesday, April 18, 2018 09:02 PM, Andrew Lunn wrote:
On Wed, Apr 18, 2018 at 02:56:01PM +0200, Andrew Lunn wrote:
On Wed, Apr 18, 2018 at 09:34:16AM +0800, Chris Ruehl wrote:
Hello,
I like to get your heads up at a regression introduced in 4.9.94
commitment lead to a kernel ops and make
On Wednesday, April 18, 2018 09:34 AM, Chris Ruehl wrote:
Hello,
I like to get your heads up at a regression introduced in 4.9.94
commitment lead to a kernel ops and make the network unusable on my MX6DL
customized board.
Race condition resume is called on startup and the phy not yet
Hello,
I like to get your heads up at a regression introduced in 4.9.94
commitment lead to a kernel ops and make the network unusable on my MX6DL
customized board.
Race condition resume is called on startup and the phy not yet initialized.
[7.313366] Unable to handle kernel NULL pointer d
