Re: [PATCH v2] toshiba_acpi: Remove unneeded u32 variables from *setup_keyboard

2015-09-25 Thread Darren Hart
On Fri, Sep 18, 2015 at 10:45:34PM -0600, Azael Avalos wrote: > The function toshiba_acpi_setup_keyboard currently has two u32 variables > used to store the Hotkey Event Type and the result of the HCI_SYSTEM_EVENT > query. > > This patch removes those two variables, as we already have a global >

Re: [PATCH v2] toshiba_acpi: Remove unneeded u32 variables from *setup_keyboard

2015-09-25 Thread Darren Hart
On Fri, Sep 18, 2015 at 10:45:34PM -0600, Azael Avalos wrote: > The function toshiba_acpi_setup_keyboard currently has two u32 variables > used to store the Hotkey Event Type and the result of the HCI_SYSTEM_EVENT > query. > > This patch removes those two variables, as we already have a global >

[PATCH v2] toshiba_acpi: Remove unneeded u32 variables from *setup_keyboard

2015-09-18 Thread Azael Avalos
The function toshiba_acpi_setup_keyboard currently has two u32 variables used to store the Hotkey Event Type and the result of the HCI_SYSTEM_EVENT query. This patch removes those two variables, as we already have a global variable named "hotkey_event_type" and the result of the HCI_SYSTEM_EVENT

[PATCH v2] toshiba_acpi: Remove unneeded u32 variables from *setup_keyboard

2015-09-18 Thread Azael Avalos
The function toshiba_acpi_setup_keyboard currently has two u32 variables used to store the Hotkey Event Type and the result of the HCI_SYSTEM_EVENT query. This patch removes those two variables, as we already have a global variable named "hotkey_event_type" and the result of the HCI_SYSTEM_EVENT