linux-kernel - Re: [stable] [RESEND][PATCH for stable 2.6.36 REGRESSION] cx25840: Prevent device probe failure due to volume control ERANGE error]

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: <1292010063.29254.13.camel@morgan.silverblock.net>
Date:	Fri, 10 Dec 2010 14:41:03 -0500
From:	Andy Walls <awalls@...metrocast.net>
To:	Greg KH <greg@...ah.com>, mchehab@...hat.com
Cc:	stable@...nel.org, linux-kernel@...r.kernel.org,
	linux-media@...r.kernel.org, hverkuil@...all.nl, gregkh@...e.de
Subject: Re: [stable] [RESEND][PATCH for stable 2.6.36 REGRESSION] cx25840:
 Prevent device probe failure due to volume control ERANGE error]

On Fri, 2010-12-10 at 10:16 -0800, Greg KH wrote:
> On Fri, Dec 10, 2010 at 08:19:57AM -0500, Andy Walls wrote:
> > Resending, since this didn't appear to make its way into in 2.6.36.2.
> 
> That's because it's not in Linus's tree, right?  I have to wait for that
> to happen before I can add it to a stable tree.

Greg,

I wasn't aware of that constraint in the process, but it makes sense to
me.


Mauro,

My understanding is that the patch has to be in one of your trees first,
and then tested in linux-next for a reasonable length of time, before
Linus will pull it into his tree.

Could you please expedite handling of this patch for 2.6.37:

	https://patchwork.kernel.org/patch/376612/

so that the regression can be fixed in 2.6.36?

Regards,
Andy

--
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/