All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Leech <christopher.leech@intel.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, netdev <netdev@vger.kernel.org>
Subject: Re: [GIT PULL] I/OAT updates for 2.6.22
Date: Wed, 02 May 2007 16:27:44 -0700	[thread overview]
Message-ID: <1178148464.16670.14.camel@cleech-lnx> (raw)
In-Reply-To: <20070502.154403.77034296.davem@davemloft.net>

On Wed, 2007-05-02 at 15:44 -0700, David Miller wrote:
> 
> Chrstopher, I really really would like you to post these patches early
> and often to netdev@vger.kernel.org especially because you are
> touching the TCP code.

You're right, I should have sent this to netdev as well.  I'm Sorry.

As for early and often, I have posted all of these patches to netdev,
and made suggested changes, and re-posted.

And when I have other networking changes, you can bet they'll get sent
to netdev for review first before I think about asking that they be
included.

> You aren't doing this, for several rounds, and just submitting your
> stuff directly to Linus, Andrew, and lkml, and it's starting to annoy
> me greatly.

For several rounds, I've been posting patches that go nowhere.  I
honestly don't care if they go straight to Linus, through you, or
through Andrew.

- Chris

      reply	other threads:[~2007-05-02 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 22:37 [GIT PULL] I/OAT updates for 2.6.22 Chris Leech
2007-05-02 22:44 ` David Miller
2007-05-02 23:27   ` Chris Leech [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1178148464.16670.14.camel@cleech-lnx \
    --to=christopher.leech@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.