linux-kernel - Re: [PATCH v3 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw

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] [day] [month] [year] [list]

Date:	Mon, 22 Feb 2016 13:22:26 -0800
From:	Darren Hart <dvhart@...radead.org>
To:	John Dahlstrom <jodarom@....ORG>
Cc:	Ike Panhc <ike.pan@...onical.com>,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] ideapad-laptop: Add ideapad Y700 (15) to the
 no_hw_rfkill DMI list

On Fri, Feb 19, 2016 at 08:01:17PM -0600, John Dahlstrom wrote:
> On Fri, 19 Feb 2016, Darren Hart wrote:
> 
> >See stable_kernel_rules.txt for how to specify relevant versions. I'm curious
> >why there is a gap from 3.18 to 4.1.
> >
> >What you probably meant was:
> >
> >Cc: <stable@...r.kernel.org> # 3.18.x
> >
> >If you are going to take this approach, you may wish to verify that this applies
> >back to 3.18, otherwise you may need to specify dependencies (also described in
> >the stable_kernel_rules).
> >
> 
> Darren,
> 
> Thank you for your assistance.
> 
> The version gap in the earlier v3 comment reflected my earlier gap in
> verification. Today I stepped through the additional kernel versions to
> confirm the patch applies successfully to those versions, and have submitted
> the patch as v4.

In this case, the patch should only have a single Cc line to stable:

Cc: <stable@...r.kernel.org> # 3.18.x

I'll make the adjustment from your v4 myself to save you the resend ;-)

> 
> Kernel version 3.18.27 already handles the 17" model of the ideapad Y700, so
> it would seem odd not to also handle the 15" model.

We backport until it doesn't apply, but shouldn't be skipping versions as we go
back, that would be simply unmaintainable. So I'll mark it as 3.18.x.

-- 
Darren Hart
Intel Open Source Technology Center