From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: NetDev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Stephen Hemminger <shemminge@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] xen-netfront: rearrange netfront_info structure to separate tx and rx
Date: Tue, 09 Oct 2007 18:08:50 -0700 [thread overview]
Message-ID: <470C2622.2080806@goop.org> (raw)
In-Reply-To: <470C20E9.9050405@garzik.org>
Jeff Garzik wrote:
> ACK but does not apply to jgarzik/netdev-2.6.git#upstream nor
> davem/net-2.6.24.git
OK, looks like you don't have the other two patches. Will post in a sec.
J
prev parent reply other threads:[~2007-10-10 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 18:44 [PATCH] xen-netfront: rearrange netfront_info structure to separate tx and rx Jeremy Fitzhardinge
2007-10-10 0:46 ` Jeff Garzik
2007-10-10 1:03 ` Jeremy Fitzhardinge
2007-10-10 1:08 ` Jeremy Fitzhardinge [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=470C2622.2080806@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminge@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 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).