linux-kernel - Re: [ 10/44] ALSA: hda - remove quirk for Dell Vostro 1015

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]

Date:	Wed, 15 Aug 2012 07:03:37 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	David Henningsson <david.henningsson@...onical.com>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, Takashi Iwai <tiwai@...e.de>
Subject: Re: [ 10/44] ALSA: hda - remove quirk for Dell Vostro 1015

On Tue, Aug 14, 2012 at 07:17:43AM +0200, David Henningsson wrote:
> On 08/14/2012 12:02 AM, Greg Kroah-Hartman wrote:
> >From: Greg KH <gregkh@...uxfoundation.org>
> >
> >3.0-stable review patch.  If anyone has any objections, please let me know.
> 
> As my previous email states, I still object to this patch being
> applied to 3.0 (it is for 3.2+). Repeating that text now:
> 
> This patch will not work on 3.0 because there is no model=auto
> fallback, so please remove it from 3.0-stable-queue.
> 
> In the original patch [1], the cc to stable was written as this:
> 
> Cc: stable@...nel.org (3.2+)
> 
> Is there a better way to specify what kernels it should and should
> not be applied to, as it doesn't seem to have worked in this case?
> 
> [1] http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=e9fc83cb2e5877801a255a37ddbc5be996ea8046

No, that's my fault, sorry, I missed that marking and shouldn't have
applied it there.  I'll go remove it right now from the queue.

greg k-h
--
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/