[PATCH 05/10] staging: unisys: visorbus: Clarify reason for pointer check in bus_destroy()

2017-02-01 Thread David Kershner
From: David Binder Clarifies why the pointer returned from visorbus_get_device_by_id() in bus_destroy() is validated. The check is performed in order to be extra careful, for the sake of added security, that the s-Par backend is providing us with a valid bus/device pair. Signed-off-by: David Bin

Re: [PATCH 05/10] staging: unisys: visorbus: Clarify reason for pointer check in bus_destroy()

2017-02-02 Thread Greg KH
On Wed, Feb 01, 2017 at 05:38:57PM -0500, David Kershner wrote: > From: David Binder > > Clarifies why the pointer returned from visorbus_get_device_by_id() in > bus_destroy() is validated. The check is performed in order to be extra > careful, for the sake of added security, that the s-Par backe

RE: [PATCH 05/10] staging: unisys: visorbus: Clarify reason for pointer check in bus_destroy()

2017-02-02 Thread Sell, Timothy C
ubject: Re: [PATCH 05/10] staging: unisys: visorbus: Clarify reason for > pointer > check in bus_destroy() > > On Wed, Feb 01, 2017 at 05:38:57PM -0500, David Kershner wrote: > > From: David Binder > > > > Clarifies why the pointer returned from visorbus_get_device_b