From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@redhat.com>
Cc: ebiederm@xmission.com, netdev@vger.kernel.org, arnd@arnd.de,
jasowang@redhat.com, ian.campbell@citrix.com,
mashirley@us.ibm.com
Subject: Re: [PATCH 0/5] macvtap fixes.
Date: Mon, 24 Oct 2011 08:31:06 +0200 [thread overview]
Message-ID: <20111024063105.GA25117@redhat.com> (raw)
In-Reply-To: <20111021.025607.2193225431127507358.davem@redhat.com>
On Fri, Oct 21, 2011 at 02:56:07AM -0400, David Miller wrote:
> From: ebiederm@xmission.com (Eric W. Biederman)
> Date: Thu, 20 Oct 2011 07:24:59 -0700
>
> >
> > This series of patches fixes a series of minor bugs in the macvtap code.
> >
> > The fixes to handle failures in newlink and the change in how we handle
> > minor device number allocations are particularly significant.
>
> Applied to net-next, thanks.
The 'Don't leak unreceived packets' patch probably makes sense in 'net'.
--
MST
prev parent reply other threads:[~2011-10-24 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 14:24 [PATCH 0/5] macvtap fixes Eric W. Biederman
2011-10-20 14:26 ` [PATCH 1/5] macvtap: Close a race between macvtap_open and macvtap_dellink Eric W. Biederman
2011-10-20 14:26 ` [PATCH 2/5] macvtap: Fix macvtap_open races in the zero copy enable code Eric W. Biederman
2011-10-20 14:27 ` [PATCH 3/5] macvtap: Don't leak unreceived packets when we delete a macvtap device Eric W. Biederman
2011-10-20 14:28 ` [PATCH 4/5] macvtap: Rewrite macvtap_newlink so the error handling works Eric W. Biederman
2011-10-20 14:29 ` [PATCH 5/5] macvtap: Fix the minor device number allocation Eric W. Biederman
2011-10-21 6:56 ` [PATCH 0/5] macvtap fixes David Miller
2011-10-24 6:31 ` Michael S. Tsirkin [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=20111024063105.GA25117@redhat.com \
--to=mst@redhat.com \
--cc=arnd@arnd.de \
--cc=davem@redhat.com \
--cc=ebiederm@xmission.com \
--cc=ian.campbell@citrix.com \
--cc=jasowang@redhat.com \
--cc=mashirley@us.ibm.com \
--cc=netdev@vger.kernel.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).