On Fri, 2014-10-17 at 09:43 +1100, Michael Ellerman wrote:
On Thu, 2014-10-16 at 15:30 -0400, Dan Streetman wrote:
Check old_devdata-dev in nx-842 driver before accessing it, as
on systems without any nx-842 hardware, the -dev will never be
set. Currently, the module will cause an oops
On Fri, 2014-10-17 at 09:43 +1100, Michael Ellerman wrote:
On Thu, 2014-10-16 at 15:30 -0400, Dan Streetman wrote:
Check old_devdata-dev in nx-842 driver before accessing it, as
on systems without any nx-842 hardware, the -dev will never be
set. Currently, the module will cause an oops
Yep, I own the driver now, I'll send a maintainers patch.
On Thu, Oct 16, 2014 at 6:52 PM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Fri, 2014-10-17 at 09:43 +1100, Michael Ellerman wrote:
On Thu, 2014-10-16 at 15:30 -0400, Dan Streetman wrote:
Check old_devdata-dev in nx-842
Check old_devdata-dev in nx-842 driver before accessing it, as
on systems without any nx-842 hardware, the -dev will never be
set. Currently, the module will cause an oops during unload
since old_devdata-dev is null.
Signed-off-by: Dan Streetman ddstr...@ieee.org
---
Also Seth and Rob, you guys
On Thu, 2014-10-16 at 15:30 -0400, Dan Streetman wrote:
Check old_devdata-dev in nx-842 driver before accessing it, as
on systems without any nx-842 hardware, the -dev will never be
set. Currently, the module will cause an oops during unload
since old_devdata-dev is null.
Hi Dan,
Patch
On Fri, 2014-10-17 at 09:43 +1100, Michael Ellerman wrote:
On Thu, 2014-10-16 at 15:30 -0400, Dan Streetman wrote:
Check old_devdata-dev in nx-842 driver before accessing it, as
on systems without any nx-842 hardware, the -dev will never be
set. Currently, the module will cause an oops
