Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-11 Thread Darren Hart
On Mon, Dec 11, 2017 at 02:48:23AM +0100, Stefan Brüns wrote: > On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > > The new notify_handler logic determining if autorelease should be used or > > not is a bit awkward, and can result in more than one call to > >

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-11 Thread Darren Hart
On Mon, Dec 11, 2017 at 02:48:23AM +0100, Stefan Brüns wrote: > On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > > The new notify_handler logic determining if autorelease should be used or > > not is a bit awkward, and can result in more than one call to > >

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-10 Thread Stefan Brüns
On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > The new notify_handler logic determining if autorelease should be used or > not is a bit awkward, and can result in more than one call to > sparse_keymap_report_event for the same event (scancode). The nesting > and long

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-10 Thread Stefan Brüns
On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > The new notify_handler logic determining if autorelease should be used or > not is a bit awkward, and can result in more than one call to > sparse_keymap_report_event for the same event (scancode). The nesting > and long

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-08 Thread Darren Hart
On Sat, Dec 09, 2017 at 12:28:18AM +0100, Stefan Brüns wrote: > On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > > The new notify_handler logic determining if autorelease should be used or > > not is a bit awkward, and can result in more than one call to > >

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-08 Thread Darren Hart
On Sat, Dec 09, 2017 at 12:28:18AM +0100, Stefan Brüns wrote: > On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > > The new notify_handler logic determining if autorelease should be used or > > not is a bit awkward, and can result in more than one call to > >

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-08 Thread Stefan Brüns
On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > The new notify_handler logic determining if autorelease should be used or > not is a bit awkward, and can result in more than one call to > sparse_keymap_report_event for the same event (scancode). The nesting > and long

Re: [PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-08 Thread Stefan Brüns
On Saturday, December 9, 2017 12:07:08 AM CET Darren Hart (VMware) wrote: > The new notify_handler logic determining if autorelease should be used or > not is a bit awkward, and can result in more than one call to > sparse_keymap_report_event for the same event (scancode). The nesting > and long

[PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-08 Thread Darren Hart (VMware)
The new notify_handler logic determining if autorelease should be used or not is a bit awkward, and can result in more than one call to sparse_keymap_report_event for the same event (scancode). The nesting and long lines also made it difficult to read. Simplify the logic by eliminating a level of

[PATCH] platform/x86: intel-vbtn: Simplify autorelease logic

2017-12-08 Thread Darren Hart (VMware)
The new notify_handler logic determining if autorelease should be used or not is a bit awkward, and can result in more than one call to sparse_keymap_report_event for the same event (scancode). The nesting and long lines also made it difficult to read. Simplify the logic by eliminating a level of