From: Greg KH <greg@kroah.com>
To: Stephen Clark <sclark46@earthlink.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel -2.6.35.13 longterm
Date: Tue, 5 Jul 2011 10:38:04 -0700 [thread overview]
Message-ID: <20110705173804.GA11421@kroah.com> (raw)
In-Reply-To: <4E134ACB.9020002@earthlink.net>
On Tue, Jul 05, 2011 at 01:32:59PM -0400, Stephen Clark wrote:
> On 07/05/2011 11:05 AM, Greg KH wrote:
> >On Tue, Jul 05, 2011 at 10:35:25AM -0400, Stephen Clark wrote:
> >
> >>Hello,
> >>
> >>Is it possible to get the following patches included in the longterm kernel
> >>2.6.35.13?
> >>
> >Possibly, but you need to email the correct person and email address,
> >none of which you did :)
> >
> >Try stable@kernel.org, and the .35-longterm maintainer (hint, it's not
> >me.)
> >
> >
> Ok - hmmm maintainers in 2.6.35.13 still lists you - but I'll look
> at a later kernel maintainers file.
It's not really obvious who is in charge, the -longterm maintainer
really should put their name there. I think for .35 it's Andi Kleen.
> >>They let linux behave according to:
> >>
> >>"Basic Requirements for IPv6 Customer Edge Routers
> >> draft-ietf-v6ops-ipv6-cpe-router-09"
> >>
> >That looks like a new feature, not a regression or bugfix, right?
> >
> >Did you read Documentation/stable_kernel_rules.txt?
> >
> >
> Not til just now. Yes it is a new feature, but with IPV6 it is seems
> that it would be of use.
> I know that my company needs it as we are moving off of FreeBSD to Linux for our
> fw/vpn/router appliance. The alternative is to just keep applying the patch myself.
As described above, new features are not for stable or longterm kernels,
sorry. I recommend just applying it yourself if you really are stuck
with the .35 kernel.
> >>From: Thomas Graf
> >>Subject: [PATCH] ipv6: add special mode accept_ra=2 to accept RA
> >>while configured as router
> >>Date: Friday, September 3, 2010 - 5:59 am
> >>
> >>
> >You forgot to mention what the git commit id this is upstream in Linus's
> >branch, and to copy the people involved in the original patch (author,
> >subsystem maintainer, etc.) to see if they agree it should go in.
> >
> >
> How in the world do you get the commit info?
>From the original patch and Linus's git tree? Also, look at
scripts/get_maintainer.pl it will show you who to send stuff to.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2011-07-05 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 14:35 kernel -2.6.35.13 longterm Stephen Clark
2011-07-05 15:05 ` Greg KH
2011-07-05 17:32 ` Stephen Clark
2011-07-05 17:38 ` Greg KH [this message]
2011-07-06 18:11 ` Andi Kleen
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=20110705173804.GA11421@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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