From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: konrad.wilk@oracle.com, jeremy@goop.org,
xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH][v3.2.y] xen-netfront: delay gARP until backend switches to Connected
Date: Fri, 15 Mar 2013 13:56:45 -0400 [thread overview]
Message-ID: <514360DD.8050406@canonical.com> (raw)
Hello,
Please consider including upstream commit
08e34eb14fe4cfd934b5c169a7682a969457c4ea in the next v3.2.y release.
It was included upstream as of v3.3-rc1. It has been tested and
confirmed to resolve http://bugs.launchpad.net/bugs/1154608 .
commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea
Author: Laszlo Ersek <lersek@redhat.com>
Date: Sun Dec 11 01:48:59 2011 +0000
xen-netfront: delay gARP until backend switches to Connected
Sincerely,
Joseph Salisbury
next reply other threads:[~2013-03-15 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 17:56 Joseph Salisbury [this message]
2013-03-18 2:19 ` [PATCH][v3.2.y] xen-netfront: delay gARP until backend switches to Connected Ben Hutchings
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=514360DD.8050406@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=ben@decadent.org.uk \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).