From: Greg KH <greg@kroah.com>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
stable@kernel.org
Subject: Re: [stable] [PATCH] fix information leak in wireless extensions on 64-bit platforms
Date: Fri, 23 Mar 2007 09:35:36 -0700 [thread overview]
Message-ID: <20070323163536.GA27015@kroah.com> (raw)
In-Reply-To: <20070323161339.GA4713@bougret.hpl.hp.com>
On Fri, Mar 23, 2007 at 09:13:39AM -0700, Jean Tourrilhes wrote:
> On Fri, Mar 23, 2007 at 04:56:24PM +0100, Johannes Berg wrote:
> > On Fri, 2007-03-23 at 08:48 -0700, Jean Tourrilhes wrote:
> >
> > > Yes, sorry for the delay, I wanted to make sure I had all the
> > > parts fully fleshed out.
> >
> > :)
> >
> > Could you maybe send yours to stable too? Both of them I guess. Or do
> > you want us (John I guess) to do that?
> >
> > johannes
>
> It seems that the lifetime of each stable branch is measured
> in weeks (apart from 2.6.16), and being an old timer, gaining a few
> weeks does not seem to me to be worth the trouble. It's not like the
> bug is entirely new.
> I'm personally more concerned about distro. If getting it into
> stable would make it go into a distro release, then I would see more
> value. It seems that it's too late for the next release of Debian or
> Fedora, and I don't know if any distro is going to be based on this
> stable branch.
Lots of distros watch the stable branches to see what they need to pick
up for their kernel releases.
So please don't just ignore them, lots of people depend on them, even
outside of the distros.
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-23 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 9:06 [PATCH] fix information leak in wireless extensions on 64-bit platforms Johannes Berg
2007-03-23 13:42 ` Johannes Berg
2007-03-23 15:42 ` John W. Linville
2007-03-23 16:24 ` Jean Tourrilhes
2007-03-23 15:48 ` Jean Tourrilhes
2007-03-23 15:56 ` Johannes Berg
2007-03-23 16:13 ` Jean Tourrilhes
2007-03-23 16:35 ` Greg KH [this message]
2007-03-23 16:53 ` Michael Buesch
2007-03-23 17:57 ` Jean Tourrilhes
2007-03-23 19:36 ` [stable] " Chris Wright
2007-03-23 20:00 ` Jean Tourrilhes
2007-03-23 20:05 ` Johannes Berg
2007-03-23 20:27 ` Michael Buesch
2007-03-23 20:31 ` Johannes Berg
2007-03-23 20:51 ` Jean Tourrilhes
2007-03-24 16:50 ` Michael Buesch
2007-03-26 15:45 ` Jean Tourrilhes
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=20070323163536.GA27015@kroah.com \
--to=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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;
as well as URLs for NNTP newsgroup(s).