From: David Miller <davem@davemloft.net>
To: vyasevic@redhat.com
Cc: netdev@vger.kernel.org, mst@redhat.com, kaber@trash.net
Subject: Re: [PATCH net-next 0/2] Add packet capture support on macvtap device
Date: Thu, 12 Dec 2013 13:39:50 -0500 (EST) [thread overview]
Message-ID: <20131212.133950.2010526901273479418.davem@davemloft.net> (raw)
In-Reply-To: <1386786431-22592-1-git-send-email-vyasevic@redhat.com>
From: Vlad Yasevich <vyasevic@redhat.com>
Date: Wed, 11 Dec 2013 13:27:09 -0500
> Change from RFC:
> - moved to the rx_handler approach.
Eric's feedback about contention is legitimate, but I think you can
deal with this in follow-on patches, so I've applied this series to
net-next.
Thanks!
prev parent reply other threads:[~2013-12-12 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 18:27 [PATCH net-next 0/2] Add packet capture support on macvtap device Vlad Yasevich
2013-12-11 18:27 ` [PATCH net-next 1/2] macvtap: Add support of packet capture " Vlad Yasevich
2013-12-12 3:45 ` Jason Wang
2013-12-12 17:23 ` Vlad Yasevich
2013-12-11 18:27 ` [PATCH net-next 2/2] macvlan: Remove custom recieve and forward handlers Vlad Yasevich
2013-12-11 21:44 ` [PATCH net-next 0/2] Add packet capture support on macvtap device David Miller
2013-12-12 18:39 ` 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=20131212.133950.2010526901273479418.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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).