From: Chicken Shack <chicken.shack@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Emil Meier <emil276me@yahoo.com>,
Linux media <linux-media@vger.kernel.org>,
francescolavra@interfree.it, stable@kernel.org
Subject: Re: alevt-dvb 1.7.0: new version, should be free from bugs now
Date: Thu, 18 Feb 2010 16:15:47 +0100 [thread overview]
Message-ID: <1266506147.4359.22.camel@brian.bconsult.de> (raw)
In-Reply-To: <20100218144021.GA15415@kroah.com>
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.
> If it is not in Linus's tree, I can not accept it.
It is there, please see above!
Instead of doing a steady maintainers job, Mauro Carvalho Chehab prefers
to play kiddish games by substituting functionable kernel patches with
his own disfunctionable ones, as you can see here:
http://www.spinics.net/lists/linux-media/msg15749.html
and here:
http://www.spinics.net/lists/linux-media/msg15761.html
The maintainers job would have been to send the commit ID to
stable@kernel.org, but foolish experiments seem to be more important
than a fix for a stable kernel.
> confused,
> greg k-h
enlightened and delighted,
Chicken Shack :) :)
stable@kernel.org Cced.....
next prev parent reply other threads:[~2010-02-18 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 21:26 alevt-dvb 1.7.0: new version, should be free from bugs now Chicken Shack
2010-02-13 9:56 ` Francesco Lavra
2010-02-13 11:11 ` Chicken Shack
2010-02-17 23:50 ` Emil Meier
2010-02-18 8:57 ` Chicken Shack
2010-02-18 10:47 ` Emil Meier
2010-02-18 14:40 ` Greg KH
2010-02-18 15:15 ` Chicken Shack [this message]
2010-02-18 15:34 ` Greg KH
2010-02-18 15:53 ` Chicken Shack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1266506147.4359.22.camel@brian.bconsult.de \
--to=chicken.shack@gmx.de \
--cc=emil276me@yahoo.com \
--cc=francescolavra@interfree.it \
--cc=greg@kroah.com \
--cc=linux-media@vger.kernel.org \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox