From: Jeff Garzik <jgarzik@pobox.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Wang Chen <wangchen@cn.fujitsu.com>,
"David S. Miller" <davem@davemloft.net>,
NETDEV <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/2] VIRTIO: Use __skb_queue_purge()
Date: Thu, 22 May 2008 22:18:42 -0400 [thread overview]
Message-ID: <48362982.1040205@pobox.com> (raw)
In-Reply-To: <200805231154.12188.rusty@rustcorp.com.au>
Rusty Russell wrote:
> On Thursday 22 May 2008 20:07:43 Wang Chen wrote:
>> Use standard routine for queue purging.
>>
>> Signed-off-by: Wang Chen <wangchen@cn.fujitsu.com>
>
> Thanks, applied.
>
> Jeff, I'm planning on final testing of my 4 pending virtio_net patches for
> 2.6.26 today: if all goes well, I'll send them in a neat batch.
It seemed more applicable as a general netdev cleanup so I also applied
it :)
In general, regardless of bus topology or whatever, net driver patches
tend to come in my direction.
Jeff
prev parent reply other threads:[~2008-05-23 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 10:07 [PATCH 1/2] VIRTIO: Use __skb_queue_purge() Wang Chen
2008-05-22 18:01 ` Jeff Garzik
2008-05-23 1:54 ` Rusty Russell
2008-05-23 2:18 ` Jeff Garzik [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=48362982.1040205@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=wangchen@cn.fujitsu.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).