linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Aaron Lu <aaron.lu@intel.com>, Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] acpi-video: Revert native brightness quirk for ThinkPad T530
Date: Sat, 17 May 2014 09:47:03 +0200	[thread overview]
Message-ID: <537713F7.4090000@redhat.com> (raw)
In-Reply-To: <13216709.cQDcpMa84k@vostro.rjw.lan>

Hi,

On 05/16/2014 10:50 PM, Rafael J. Wysocki wrote:
> On Friday, May 16, 2014 09:10:41 PM Hans de Goede wrote:
>> Seems it helps some users, but causes issues for other users:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1089545
>>
>> So lets drop it for now until we've figured out a better fix.
> 
> So you hadn't even waited for all of your users to have a chance to test the
> blacklist patch and you asked me to push it for -rc5 nevertheless.  You don't
> even realize how disappointing that is.

That is not how it happened, after the patch going out a new user with a T530
showed up, who did not have any problems before so never was part of the bug
reports about this before, but got problems after the patch.
So it seems that different T530's behave differently.

This may have something todo with whether they were booted in EFI mode or not,
or maybe there are just 2 different revisions out there.

Note that this is all not in vain:

1) We would have never heard from that user without the patch
2) The behavior the patch causes is going to be the default in 3.16, so now we've
caught it early and can work on a fix before 3.16-rc1.

> I had to rebase this patch, so it has to go through autobuild testing and
> I'll try to add it to my -rc6 pull request, but I'm not going to take any new
> blacklist entries for anything later than -rc4 in the future.  And don't even
> *try* to argue with that.

I can see that being reasonable, although I believe this time it does actually work
in out advantage, esp. with the default behavior change planned for 3.15.

Regards,

Hans


> 
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>>  drivers/acpi/video.c | 8 --------
>>  1 file changed, 8 deletions(-)
>>
>> diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
>> index 0fec70d..8309100 100644
>> --- a/drivers/acpi/video.c
>> +++ b/drivers/acpi/video.c
>> @@ -516,14 +516,6 @@ static struct dmi_system_id video_dmi_table[] __initdata = {
>>  	},
>>  	{
>>  	 .callback = video_set_use_native_backlight,
>> -	 .ident = "ThinkPad T530",
>> -	 .matches = {
>> -		DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
>> -		DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad T530"),
>> -		},
>> -	},
>> -	{
>> -	 .callback = video_set_use_native_backlight,
>>  	 .ident = "ThinkPad W530",
>>  	 .matches = {
>>  		DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
>>
> 

      reply	other threads:[~2014-05-17  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 19:10 [PATCH] acpi-video: Revert native brightness quirk for ThinkPad T530 Hans de Goede
2014-05-16 20:50 ` Rafael J. Wysocki
2014-05-17  7:47   ` Hans de Goede [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=537713F7.4090000@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=aaron.lu@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).