Re: [PATCH 1/5] staging: lirc_serial: Fix init/exit order

2012-03-01 Thread Jonathan Nieder
Hi Ben, Ben Hutchings wrote[1]: Currently the module init function registers a platform_device and only then allocates its IRQ and I/O region. This allows allocation to race with the device's suspend() function. Instead, allocate resources in the platform driver's probe() function and free

Re: [PATCH 1/5] staging: lirc_serial: Fix init/exit order

2012-03-01 Thread Ben Hutchings
On Thu, 2012-03-01 at 21:45 -0600, Jonathan Nieder wrote: [...] From http://bugs.debian.org/645811 I see that you tested these patches: affc9a0d59ac [media] staging: lirc_serial: Do not assume error codes returned by request_irq() 9b98d6067971 [media] staging: lirc_serial:

Re: [PATCH 1/5] staging: lirc_serial: Fix init/exit order

2012-03-01 Thread VDR User
I have a few questions about lirc_serial... It seems that it's now a part of v4l and currently residing in the driver staging area. I was told it will not move from staging until it has been converted to rc_core. I was also told there are no plans for anyone to do this so it would seem

[PATCH 1/5] staging: lirc_serial: Fix init/exit order

2011-11-15 Thread Ben Hutchings
Currently the module init function registers a platform_device and only then allocates its IRQ and I/O region. This allows allocation to race with the device's suspend() function. Instead, allocate resources in the platform driver's probe() function and free them in the remove() function. The