linux-kernel - Re: [stable] [PATCH] [stable-37] ideapad: read brightness setting when have brightness key notify

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D759675.8020600@canonical.com>
Date:	Tue, 08 Mar 2011 10:37:41 +0800
From:	Ike Panhc <ike.pan@...onical.com>
To:	Greg KH <greg@...ah.com>
CC:	stable@...nel.org, Matthew Garrett <mjg@...hat.com>,
	linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org
Subject: Re: [stable] [PATCH] [stable-37] ideapad: read brightness setting
 when have brightness key notify

On 03/08/2011 12:18 AM, Greg KH wrote:
> On Mon, Mar 07, 2011 at 06:35:25PM +0800, Ike Panhc wrote:
>> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=25922
>>
>> On ideapad Y530, the brightness key notify will be blocked if the last notify
>> is not responsed by getting the brightness value. Read value when we get the
>> notify shall fix the problem and will not have any difference on other ideapads.
>>
>> This patch is made against 2.6.37.y and this bug impacts kernel after 2.6.37.
>>
>> The equivalent-fix patch is not in upstream yet. Since the policy of stable tree
>> is changed and .38 kernel is going to finalize.
> 
> What "policy of the stable tree is changed"?  Huh?

I thought we will have stable release on lastest kernel only[1]. Since the .38 is
going to release soon. It seems I do not have much time for .37 stable release.

I hope I do not miss something.

[1] https://lkml.org/lkml/2010/12/2/388

> 
>> I think to post this patch for stable kernel now should be a good
>> idea.
> 
> Have you not read the Documentation/stable_kernel_rules.txt and seen
> that this is totally and completly not allowed?  Why is it suddenly not
> true?
> 
> confused,

Sorry about the confusing. The same patch for upstream is posted[2] but not merged
yet. It looks like a now-or-never situation to me. That's why I post and write the
concerns in comment.

[1] https://lkml.org/lkml/2011/2/23/171

> 
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/