On Tue, Apr 04, 2017 at 01:14:36PM +0300, Jala - wrote:
> The issue should be corrected in the following.
Unfortunately not. See the body of the message and note that there are no
leading tabs in the DMI_MATCH block.
I recommend sending the message to yourself and attempting to apply the patch.
Once that works, send it to the list.
If you aren't sure how to resolve the problem after reading the Documentation I
linked to, feel free to reach out to me privately for assistance.
Regards,
--
Darren Hart
VMware Open Source Technology Center
>
> ---
> drivers/platform/x86/asus-nb-wmi.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/platform/x86/asus-nb-wmi.c
> b/drivers/platform/x86/asus-nb-wmi.c
> index dea98ffb6f60..1ae58d906536 100644
> --- a/drivers/platform/x86/asus-nb-wmi.c
> +++ b/drivers/platform/x86/asus-nb-wmi.c
> @@ -144,6 +144,15 @@ static const struct dmi_system_id asus_quirks[] = {
> },
> {
> .callback = dmi_matched,
> + .ident = "ASUSTeK COMPUTER INC. X302UA",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "X302UA"),
> + },
> + .driver_data = &quirk_asus_wapf4,
> + },
> + {
> + .callback = dmi_matched,
> .ident = "ASUSTeK COMPUTER INC. X401U",
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> --
> 2.11.0.windows.3
>
