From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Alistair Woodman <awoodman@isc.org>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] closer ties to ltsi?
Date: Fri, 2 Mar 2012 07:43:02 -0800 [thread overview]
Message-ID: <20120302154302.GD27141@kroah.com> (raw)
In-Reply-To: <CAA93jw7Hm+KNRUEAinod2Djs2upwN_yhWCDk7wiGF3HH-qCVhA@mail.gmail.com>
On Fri, Mar 02, 2012 at 02:33:25AM -0800, Dave Taht wrote:
> Dear Greg:
>
> What ltsi is up to:
>
> http://ltsi.linuxfoundation.org/what-is-ltsi
>
> is orthogonal to what we are up to, in that they are trying to produce
> a usable, stable tree that can be used in a lot of CE devices, and we
> are trying to push the bleeding edge in finding, fixing, and testing
> things that would be good to have deployed in a lot of CE devices at
> least on the bufferbloat, security, and network - especially ipv6 -
> fronts.
>
> How to faster get stuff from "R&D" to deployment is always on my mind.
> I'm very happy to be successfully tracking the 3.3 process 'live' at
> the moment with cerowrt. I imagine the next 'stable'
> kernel chosen will be 3.3 or 3.4 based.
If you do all of your work upstream in the main kernel.org kernel, then
LTSI can backport your changes as needed to their kernels. I recommend
doing that.
best of luck,
greg k-h
next prev parent reply other threads:[~2012-03-02 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 10:33 Dave Taht
2012-03-02 15:43 ` Greg KH [this message]
2012-03-02 16:13 ` Jim Gettys
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120302154302.GD27141@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=awoodman@isc.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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