Re: [PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer (v3)

2017-05-01 Thread Sean Young
On Mon, May 01, 2017 at 03:32:34PM +0200, David Härdeman wrote: > ir_lirc_register() currently creates its own lirc_buffer before > passing the lirc_driver to lirc_register_driver(). > > When a module is later unloaded, ir_lirc_unregister() gets called > which performs a call to

[PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer (v3)

2017-05-01 Thread David Härdeman
ir_lirc_register() currently creates its own lirc_buffer before passing the lirc_driver to lirc_register_driver(). When a module is later unloaded, ir_lirc_unregister() gets called which performs a call to lirc_unregister_driver() and then free():s the lirc_buffer. The problem is that: a) there

Re: [PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer (v2)

2017-05-01 Thread David Härdeman
On Mon, May 01, 2017 at 01:22:21PM +0100, Sean Young wrote: >On Sat, Apr 29, 2017 at 11:22:28PM +0200, David Härdeman wrote: >> ir_lirc_register() currently creates its own lirc_buffer before >> passing the lirc_driver to lirc_register_driver(). >> >> When a module is later unloaded,

Re: [PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer (v2)

2017-05-01 Thread Sean Young
On Sat, Apr 29, 2017 at 11:22:28PM +0200, David Härdeman wrote: > ir_lirc_register() currently creates its own lirc_buffer before > passing the lirc_driver to lirc_register_driver(). > > When a module is later unloaded, ir_lirc_unregister() gets called > which performs a call to

[PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer (v2)

2017-04-29 Thread David Härdeman
ir_lirc_register() currently creates its own lirc_buffer before passing the lirc_driver to lirc_register_driver(). When a module is later unloaded, ir_lirc_unregister() gets called which performs a call to lirc_unregister_driver() and then free():s the lirc_buffer. The problem is that: a) there

Re: [PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer

2017-04-29 Thread David Härdeman
On Fri, Apr 28, 2017 at 07:04:09PM +0200, David Härdeman wrote: >ir_lirc_register() currently creates its own lirc_buffer before >passing the lirc_driver to lirc_register_driver(). > >When a module is later unloaded, ir_lirc_unregister() gets called >which performs a call to

Re: [PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer

2017-04-28 Thread David Härdeman
On Fri, Apr 28, 2017 at 07:04:09PM +0200, David Härdeman wrote: >ir_lirc_register() currently creates its own lirc_buffer before >passing the lirc_driver to lirc_register_driver(). > >When a module is later unloaded, ir_lirc_unregister() gets called >which performs a call to

[PATCH] ir-lirc-codec: let lirc_dev handle the lirc_buffer

2017-04-28 Thread David Härdeman
ir_lirc_register() currently creates its own lirc_buffer before passing the lirc_driver to lirc_register_driver(). When a module is later unloaded, ir_lirc_unregister() gets called which performs a call to lirc_unregister_driver() and then free():s the lirc_buffer. The problem is that: a) there