Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cerowrt-devel@lists.bufferbloat.net, Alistair Woodman <awoodman@isc.org>
Subject: Re: [Cerowrt-devel] closer ties to ltsi?
Date: Fri, 02 Mar 2012 11:13:59 -0500	[thread overview]
Message-ID: <4F50F1C7.4080401@freedesktop.org> (raw)
In-Reply-To: <20120302154302.GD27141@kroah.com>

On 03/02/2012 10:43 AM, Greg KH wrote:
> 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.
>
>
That's what Dave has been doing, to the extent possible; it's a bit of a
PITA, since the MIPS/OpenWrt folks tend not to quite keep up with x86. 
And BQL (in 3.3) is essential to bufferbloat work.
                    - Jim


      reply	other threads:[~2012-03-02 16:14 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
2012-03-02 16:13   ` Jim Gettys [this message]

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=4F50F1C7.4080401@freedesktop.org \
    --to=jg@freedesktop.org \
    --cc=awoodman@isc.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=gregkh@linuxfoundation.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