Re: [PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-16 Thread Sergei Shtylyov
Hello. On 15-01-2013 8:58, Tony Prisk wrote: Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -EADDRNOTAVAIL. You meant

Re: [PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-16 Thread Sergei Shtylyov
Hello. On 15-01-2013 8:58, Tony Prisk wrote: Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -EADDRNOTAVAIL. You meant

Re: [PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-14 Thread Tony Prisk
On Tue, 2013-01-15 at 17:58 +1300, Tony Prisk wrote: > Memory mapped via ioremap call is never released. Rather than add an > iounmap call, change allocation function to devm_request_and_ioremap. > > Also, change the error on failure for this call to -EBUSY rather than > -EADDRNOTAVAIL. Grr.. I

[PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-14 Thread Tony Prisk
Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -EADDRNOTAVAIL. Signed-off-by: Tony Prisk --- drivers/tty/serial/vt8500_serial.c |

Re: [PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-14 Thread Sergei Shtylyov
Hello. On 14-01-2013 6:04, Tony Prisk wrote: Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -ENOMEM. Not really well

Re: [PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-14 Thread Sergei Shtylyov
Hello. On 14-01-2013 6:04, Tony Prisk wrote: Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -ENOMEM. Not really well

[PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-14 Thread Tony Prisk
Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -EADDRNOTAVAIL. Signed-off-by: Tony Prisk li...@prisktech.co.nz ---

Re: [PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-14 Thread Tony Prisk
On Tue, 2013-01-15 at 17:58 +1300, Tony Prisk wrote: Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -EADDRNOTAVAIL. Grr.. I

[PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-13 Thread Tony Prisk
Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -ENOMEM. Signed-off-by: Tony Prisk --- drivers/tty/serial/vt8500_serial.c |4 ++--

[PATCH 2/4] serial: vt8500: ioremap'd resource is never freed

2013-01-13 Thread Tony Prisk
Memory mapped via ioremap call is never released. Rather than add an iounmap call, change allocation function to devm_request_and_ioremap. Also, change the error on failure for this call to -EBUSY rather than -ENOMEM. Signed-off-by: Tony Prisk li...@prisktech.co.nz ---