public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruce <bruce.ma@canonical.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: platform-driver-x86@vger.kernel.org,
	ibm-acpi-devel@lists.sourceforge.net,
	Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
	linux-kernel@vger.kernel.org
Subject: Re: Patch for thinkpad-acpi.c
Date: Wed, 29 May 2013 11:54:57 +0800	[thread overview]
Message-ID: <51A57C11.40403@canonical.com> (raw)
In-Reply-To: <87r4gr9z5o.fsf@nemi.mork.no>

Hi, Bjorn

Thank your advice .
I will modify my code, then try to submit again.

Bruce.Ma
May 29,2013


On 05/28/2013 06:28 PM, Bjørn Mork wrote:
> Bruce <bruce.ma@canonical.com> writes:
>
>> +struct blacklist lenovo_blacklist[] = {
>> +  {
>> +    .model_s = "Lenovo LM490s",
>> +    .nummodel_s = "814YG01",
>> +  },
>
> The driver already has a list of LED support per model in the 
>
>   static const struct tpacpi_quirk led_useful_qtable[] __initconst = {}
>
> array.   Why do you duplicate this with lots of new model checking code
> instead of just using the code that's already there?
>
>>  static void led_exit(void)
>>  {
>> +        if (no_led == 1 ) {
>
> The driver already has provisions for signalling that LEDs are
> unsupported through the 'led_supported' variable.  Why do you add
> another variable, and duplicate testing in every access function?
>
> But I don't think this part is needed at all, as long as you set up the
> proper LED map in led_useful_qtable.
>
>
>
> Bjørn


      reply	other threads:[~2013-05-29  3:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  9:22 Patch for thinkpad-acpi.c Bruce
2013-05-28 10:28 ` Bjørn Mork
2013-05-29  3:54   ` Bruce [this message]

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=51A57C11.40403@canonical.com \
    --to=bruce.ma@canonical.com \
    --cc=bjorn@mork.no \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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