From: David Miller <davem@davemloft.net>
To: jeff@garzik.org
Cc: ossthema@de.ibm.com, raisch@de.ibm.com, themann@de.ibm.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
meder@de.ibm.com, tklein@de.ibm.com, gallatin@myri.com,
stefan.roscher@de.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/1] lro: Generic Large Receive Offload for TCP traffic
Date: Thu, 09 Aug 2007 00:03:42 -0700 (PDT) [thread overview]
Message-ID: <20070809.000342.21950010.davem@davemloft.net> (raw)
In-Reply-To: <46BAB4AF.7010001@garzik.org>
From: Jeff Garzik <jeff@garzik.org>
Date: Thu, 09 Aug 2007 02:31:11 -0400
> Either way, I'll want you to push to Linus before I do, when the next
> merge window opens.
No problem.
prev parent reply other threads:[~2007-08-09 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 12:41 [PATCH 0/1] lro: Generic Large Receive Offload for TCP traffic Jan-Bernd Themann
2007-08-09 6:11 ` David Miller
2007-08-09 6:31 ` Jeff Garzik
2007-08-09 7:03 ` David Miller [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=20070809.000342.21950010.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gallatin@myri.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=meder@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=ossthema@de.ibm.com \
--cc=raisch@de.ibm.com \
--cc=stefan.roscher@de.ibm.com \
--cc=themann@de.ibm.com \
--cc=tklein@de.ibm.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;
as well as URLs for NNTP newsgroup(s).