X86 platform drivers
 help / color / mirror / Atom feed
From: Kyle Evans <kvans32@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: platform-driver-x86@vger.kernel.org, rjw@rjwysocki.net
Subject: Re: [PATCHv4] hp-wmi: limit hotkey enable
Date: Fri, 11 Sep 2015 10:05:42 -0500	[thread overview]
Message-ID: <55F2EDC6.9090504@gmail.com> (raw)
In-Reply-To: <20150910212147.GA117960@vmdeb7>

On 09/10/2015 04:21 PM, Darren Hart wrote:
> On Thu, Sep 10, 2015 at 12:45:00PM -0500, Kyle Evans wrote:
>> Do not write initialize magic on systems that do not have
>> feature query 0xb. Fixes Bug #82451.
>>
>> Redefine FEATURE_QUERY to align with 0xb and FEATURE2 with 0xd
>> for code clearity.
>>
>> Add a new test function, hp_wmi_bios_2008_later() & simplify
>> hp_wmi_bios_2009_later(), which fixes a bug in cases where
>> an improper value is returned. Probably also fixes Bug #69131.
>>
>> Signed-off-by: Kyle Evans <kvans32@gmail.com>
>> ---
>>   Since v1:
>>   - Refactored feature query 0xb into separate function
>>   - Redefine FEATURE_QUERY to align with 0xb and FEATURE2 with 0xd
>>
>>   Since v2:
>>   - Simplify hp_wmi_bios_200x_later functions. No longer returns true
>>   (4) when the test fails. However, if state is somehow useful, that is lost.
>>
>>   Since v3:
>>   - Fix whitespace, email client reformatting.
>
> Thanks, this one applies cleanly, however:
>
> drivers/platform/x86/hp-wmi.c: In function ‘hp_wmi_input_setup’:
> drivers/platform/x86/hp-wmi.c:675:2: error: implicit declaration of function ‘hp_wmi_2008_later’ [-Werror=implicit-function-declaration]
>    if (!hp_wmi_bios_2009_later() && hp_wmi_2008_later())
>    ^
> drivers/platform/x86/hp-wmi.c: At top level:
> drivers/platform/x86/hp-wmi.c:299:19: warning: ‘hp_wmi_bios_2008_later’ defined but not used [-Wunused-function]
>   static int __init hp_wmi_bios_2008_later(void)
>
> Looks like you missed "bios" in the call to hp_wmi_bios_2008_later. Which
> suggests this version was not compile tested. As I cannot test the code myself
> without hardware, I depend on submitters even more to do the testing, so it is
> really important that you have tested the exact patch that I send to Linus.
>
Sorry for all the rookie mistakes.
I did run a compile and reboot script. Unfortunately, the error logic 
was commented out when I was debugging the reboot code and never 
re-enabled. Lesson learned. I'm on it.

  reply	other threads:[~2015-09-11 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 14:56 [PATCH] hp-wmi: limit hotkey enable Kyle Evans
2015-08-28 18:42 ` Darren Hart
2015-08-29 15:26   ` Kyle Evans
2015-09-06 18:03     ` Darren Hart
2015-09-08 15:58       ` Kyle Evans
2015-09-08 18:29       ` Kyle Evans
2015-09-08 20:22         ` Darren Hart
2015-09-09 20:32           ` Kyle Evans
2015-09-10  3:19             ` Darren Hart
2015-09-10 16:45               ` [PATCHv3] " Kyle Evans
2015-09-10 17:46                 ` Darren Hart
2015-09-10 19:47                   ` Kyle Evans
2015-09-10 17:45               ` [PATCHv4] " Kyle Evans
2015-09-10 21:21                 ` Darren Hart
2015-09-11 15:05                   ` Kyle Evans [this message]
2015-09-11 15:40               ` [PATCHv5] " Kyle Evans
2015-09-11 15:55                 ` Darren Hart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55F2EDC6.9090504@gmail.com \
    --to=kvans32@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox