From: Len Brown <lenb@kernel.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>, showard314@gmail.com
Subject: Re: [PATCH] ACPI video: ignore buggy _BQC
Date: Wed, 24 Jun 2009 02:09:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0906240209160.32742@localhost.localdomain> (raw)
In-Reply-To: <1245820142.15520.112.camel@rzhang-dt>
scripts/checkpatch.pl
ERROR: code indent should use tabs where possible
#38: FILE: drivers/acpi/video.c:613:
+ ^I^I^Ifor (i = 2; i < device->brightness->count; i++)$
ERROR: code indent should use tabs where possible
#39: FILE: drivers/acpi/video.c:614:
+ ^I^I^I if (device->brightness->levels[i] == *level) {$
ERROR: code indent should use tabs where possible
#40: FILE: drivers/acpi/video.c:615:
+ ^I^I^I^I device->brightness->curr = *level;$
ERROR: code indent should use tabs where possible
#41: FILE: drivers/acpi/video.c:616:
+ ^I^I^I return 0;$
ERROR: code indent should use tabs where possible
#42: FILE: drivers/acpi/video.c:617:
+ ^I^I^I }$
ERROR: code indent should use tabs where possible
#43: FILE: drivers/acpi/video.c:618:
+ ^I^I^I/* BQC returned an invalid level. Stop using it. */$
ERROR: code indent should use tabs where possible
#44: FILE: drivers/acpi/video.c:619:
+ ^I^I^IACPI_WARNING((AE_INFO, "%s returned an invalid level",$
ERROR: code indent should use tabs where possible
#45: FILE: drivers/acpi/video.c:620:
+ ^I^I^I^I buf));$
ERROR: code indent should use tabs where possible
#46: FILE: drivers/acpi/video.c:621:
+ ^I^I^Idevice->cap._BQC = device->cap._BCQ = 0;$
total: 9 errors, 0 warnings, 24 lines checked
next prev parent reply other threads:[~2009-06-24 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 5:09 [PATCH] ACPI video: ignore buggy _BQC Zhang Rui
2009-06-24 6:09 ` Len Brown [this message]
2009-06-24 7:17 ` Zhang Rui
2009-06-24 17:37 ` Len Brown
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=alpine.LFD.2.00.0906240209160.32742@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=showard314@gmail.com \
/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