Staging: dgap: RFC

2014-04-17 Thread Mark Hounschell
The latest staging tree based on 3.15-rc1 has revealed a bug that I
introduced into the dgap driver way back. Various oops occur when
loading and unloading the driver multiple times in succession. The oops
never actually indicate anything dgap driver related. When I send a
patch to fix the problem, since the oops is rarely the same, do I need
to include an oops message with my patch or should I just indicate
various oops?

Thanks
Mark
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel


Re: Staging: dgap: RFC

2014-04-17 Thread Dan Carpenter
On Thu, Apr 17, 2014 at 09:07:12AM -0400, Mark Hounschell wrote:
 The latest staging tree based on 3.15-rc1 has revealed a bug that I
 introduced into the dgap driver way back. Various oops occur when
 loading and unloading the driver multiple times in succession. The oops
 never actually indicate anything dgap driver related. When I send a
 patch to fix the problem, since the oops is rarely the same, do I need
 to include an oops message with my patch or should I just indicate
 various oops?

These things are not hard and fast rules.  Do whatever makes sense.
Give reporter credit if anyone else discovered it.

regards,
dan carpenter

___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel