From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Chris Wright <chrisw@sous-sol.org>,
NetDev <netdev@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] Re: Xen netfront fixes for changed skbuff in net-2.6.22.git
Date: Wed, 28 Mar 2007 14:55:56 -0700 [thread overview]
Message-ID: <460AE46C.9050805@goop.org> (raw)
In-Reply-To: <20070328214604.GA10231@gondor.apana.org.au>
Herbert Xu wrote:
> I've had a look at now and you can just stuff it into one of the other
> pointers that's still there. We just need to make sure that it is
> reset properly before we feed the packet into the stack. The pointer
> skb->dev is one candidate but there are plenty of others.
>
Hm, I was wondering if there's a nicer way of getting the same result.
Does it need to be done that way?
Thanks,
J
next prev parent reply other threads:[~2007-03-28 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 18:36 Xen netfront fixes for changed skbuff in net-2.6.22.git Jeremy Fitzhardinge
2007-03-28 21:46 ` Herbert Xu
2007-03-28 21:55 ` Jeremy Fitzhardinge [this message]
2007-03-28 22:10 ` [Xen-devel] " Herbert Xu
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=460AE46C.9050805@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xensource.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).