LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
Justin Forbes <jmforbes@linuxtx.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
"Theodore Ts'o" <tytso@mit.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
Dave Jones <davej@redhat.com>,
Chuck Wolber <chuckw@quantumlinux.com>,
Chris Wedgwood <reviews@ml.cw.f00f.org>,
Chuck Ebbert <cebbert@redhat.com>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
alan@lxorguk.ukuu.org.uk,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>
Subject: Re: [patch 0/9] 2.6.19-stable review
Date: Fri, 02 Mar 2007 20:48:54 -0500 [thread overview]
Message-ID: <45E8D406.7010008@linuxtv.org> (raw)
In-Reply-To: <20070303012300.GD6496@suse.de>
Greg KH wrote:
> On Tue, Feb 27, 2007 at 03:23:05PM -0500, Michael Krufky wrote:
>> Greg KH wrote:
>>> This is the start of the stable review cycle for the 2.6.19.6 release.
>>>
>>> This will probably be the last release of the 2.6.19-stable series, so
>>> if there are patches that you feel should be applied to that tree,
>>> please let me know.
>>>
>>> There are 9 patches in this series, all will be posted as a response to
>>> this one. If anyone has any issues with these being applied, please let
>>> us know. If anyone is a maintainer of the proper subsystem, and wants
>>> to add a Signed-off-by: line to the patch, please respond with it.
>>>
>>> These patches are sent out with a number of different people on the Cc:
>>> line. If you wish to be a reviewer, please email stable@kernel.org to
>>> add your name to the list. If you want to be off the reviewer list,
>>> also email us.
>>>
>>> Responses should be made by Thursday March 1 00:00 UTC. Anything
>>> received after that time might be too late.
>>>
>>> The whole patch set can be downloaded at:
>>> kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.19.6-rc1.gz
>>>
>>> thanks,
>>>
>>> the -stable release team
>> Greg,
>>
>> I still have three DVB patches that need to go to 2.6.19.y, the dvbdev patch
>> being most important. I sent this dvbdev patch to you during the 2.6.19.5
>> review period and expected it to surface this time around, but maybe our email
>> paths have crossed.
>>
>> Since I am unable to send patches inline from my current location, I've posted
>> the three pending patches for 2.6.19.y here:
>>
>> http://linuxtv.org/~mkrufky/stable/2.6.19.y/
>>
>> Please add these if possible. Again, the
>> "dvbdev-fix-illegal-re-usage-of-fileoperations-struct" patch is the most
>> important one of these.
>
> Argh, I forgot these :(
>
> Do you want me to do a new 2.6.19-stable release with these patches in
> it? It's my fault I didn't get this in, so I don't really mind if you
> feel it is important enough (it doesn't take that long to spin another
> kernel release.)
>
> thanks,
>
> greg k-h
The dvbdev patch is pretty important, fixes a horrible problem, although the case for
it to occur is rare. The other two patches are of the "obviously correct - minimal change"
type.
If it isnt too much trouble, then yes, it is worth it to push a new release because of the
dvbdev patch.
However, please chop the "backported from" and "cherry picked from" lines from those patches.
I cherry-picked them from Mauro's tree, but he wiped it out and re-pushed those changes in
before Linus merged them.... so, the actual changesets in Linus' tree have different hashes.
(i removed those old hashes from the patches that I posted on linuxtv.org)
As for the 2.6.20.y patches, should I email those to you inline or can you just grab them from
the linuxtv.org www server? ( http://linuxtv.org/~mkrufky/stable/2.6.20.y/ )
Thanks,
Mike Krufky
next prev parent reply other threads:[~2007-03-03 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070226235248.438556696@mini.kroah.org>
2007-02-27 0:05 ` [patch 0/9] 2.6.19-stable review Greg KH
2007-02-27 0:06 ` [patch 1/9] fix umask when noACL kernel meets extN tuned for ACLs Greg KH
2007-02-27 0:28 ` Andreas Gruenbacher
2007-02-27 0:06 ` [patch 2/9] Backport of psmouse suspend/shutdown cleanups Greg KH
2007-02-27 0:06 ` [patch 3/9] fix memory corruption from misinterpreted bad_inode_ops return values (CVE-2006-5753) Greg KH
2007-02-27 0:06 ` [patch 4/9] netpoll: drivers must not enable IRQ unconditionally in their NAPI handler Greg KH
2007-02-27 0:06 ` [patch 5/9] hda-intel - Dont try to probe invalid codecs Greg KH
2007-02-27 0:06 ` [patch 6/9] Fix oops when Windows server sent bad domain name null terminator Greg KH
2007-02-27 0:06 ` [patch 7/9] USB: usbnet driver bugfix Greg KH
2007-02-27 0:06 ` [patch 8/9] hda-codec - Dont return error at initialization of modem codec Greg KH
2007-02-27 0:06 ` [patch 9/9] Missing critical phys_to_virt in lib/swiotlb.c Greg KH
2007-02-27 2:47 ` [patch 0/9] 2.6.19-stable review (mmc: Power quirk for ENE controllers) Darren Salt
2007-02-27 20:23 ` [patch 0/9] 2.6.19-stable review Michael Krufky
2007-03-03 1:23 ` Greg KH
2007-03-03 1:48 ` Michael Krufky [this message]
2007-03-03 7:48 ` Greg KH
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=45E8D406.7010008@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=chuckw@quantumlinux.com \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=jmforbes@linuxtx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=reviews@ml.cw.f00f.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=zwane@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).