From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.gmx.net ([213.165.64.20]:58750 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1758537Ab0BRPxf (ORCPT ); Thu, 18 Feb 2010 10:53:35 -0500 Subject: Re: alevt-dvb 1.7.0: new version, should be free from bugs now From: Chicken Shack To: Greg KH Cc: Emil Meier , Linux media , francescolavra@interfree.it, stable@kernel.org In-Reply-To: <20100218153441.GB20850@kroah.com> References: <592995.76165.qm@web37603.mail.mud.yahoo.com> <1266483476.1690.50.camel@brian.bconsult.de> <20100218144021.GA15415@kroah.com> <1266506147.4359.22.camel@brian.bconsult.de> <20100218153441.GB20850@kroah.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 18 Feb 2010 16:53:25 +0100 Message-ID: <1266508405.4772.2.camel@brian.bconsult.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Am Donnerstag, den 18.02.2010, 07:34 -0800 schrieb Greg KH: > On Thu, Feb 18, 2010 at 04:15:47PM +0100, Chicken Shack wrote: > > Am Donnerstag, den 18.02.2010, 06:40 -0800 schrieb Greg KH: > > > On Thu, Feb 18, 2010 at 09:57:56AM +0100, Chicken Shack wrote: > > > > For Greg Kroah-Hartman: > > > > > > > > This one should go into kernel 2.6.32, just to close a gap of kernel > > > > regressions: > > > > > > > > http://linuxtv.org/hg/v4l-dvb/rev/2dfe2234e7ea > > > > > > I have no idea what you are asking me to do here. > > > > > > If you need a patch in the -stable tree, send the git commit id of the > > > patch that is in Linus's tree to the stable@kernel.org email address. > > > > OK. So this is a bit new and confusing, and it is definitely not my job, > > as there are so-called MAINTAINERS for that, but I will try my best: > > > > > > Here is the link: > > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=691c9ae099b9bcb5c27125af00a4a90120977458 > > > > and this ought to be the commit id: > > > > commit 691c9ae099b9bcb5c27125af00a4a90120977458 > > > > SOB etc. please see link. > > That patch is already queued up for the next 2.6.32-stable kernel > release. The people involved in that patch should have already gotten > an email saying so. Thanks! This is the only thing I wanted to make sure. Regards CS