netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: davem@redhat.com, netdev@oss.sgi.com
Subject: Re: Please route new work through -mm tree?
Date: Wed, 29 Sep 2004 11:13:55 -0700	[thread overview]
Message-ID: <415AFB63.7010107@us.ibm.com> (raw)
In-Reply-To: <1096481023.8636.7.camel@localhost.localdomain>

Stephen Hemminger wrote:
> There is lots of stuff going on that has a potential to make things less
> stable. How about routing any future TCP, fib, statistics, stuff through
> Andrew's tree and not directly to Linus. That way we have some buffer
> and can stablize some more. Alternatively, Dave you could publize your
> staging area some more.

That would help us out a bit - we're testing mainline
and -mm regularly. This came up for me yesterday, too,
with Dave's tso patches (which I'm testing right now,
after getting past some hw issues). I was going to
suggest a separate bk tree or something that would
hold this stuff till it stabilized, before it needed
to go into mainline. Having that picked up by mm would
help us to increase coverage quite a bit.

thanks,
Nivedita

  reply	other threads:[~2004-09-29 18:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 18:03 Please route new work through -mm tree? Stephen Hemminger
2004-09-29 18:13 ` Nivedita Singhvi [this message]
2004-09-29 18:23   ` Marcos D. Marado Torres
2004-09-29 20:22   ` David S. Miller
2004-09-29 20:58     ` Nivedita Singhvi
2004-09-29 21:24       ` David S. Miller
2004-09-29 21:37         ` Jeff Garzik
2004-09-29 21:44           ` David S. Miller
2004-09-29 22:30             ` Jeff Garzik
2004-09-29 21:12     ` Gerrit Huizenga
2004-09-29 20:19 ` David S. Miller

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=415AFB63.7010107@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=davem@redhat.com \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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).