From: Laszlo Ersek <lersek@redhat.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com, konrad.wilk@oracle.com
Subject: Re: [PATCH net-next v4] xen-netfront: delay gARP until backend switches to Connected
Date: Mon, 02 Jan 2012 18:14:33 +0100 [thread overview]
Message-ID: <4F01E5F9.8060006@redhat.com> (raw)
In-Reply-To: <4F01F1BC020000780006A1A8@nat28.tlf.novell.com>
On 01/02/12 18:04, Jan Beulich wrote:
> I've got both backend and frontend changes ready for that tree - all I
> was really after was some double checking that both changes logically
> apply to that tree.
I think (hope :)) so. In the RHEL-5 kernel they seem to work together fine.
Thanks
Laszlo
prev parent reply other threads:[~2012-01-02 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 11:38 [PATCH v3 REPOST] xen-netfront: delay gARP until backend switches to Connected Laszlo Ersek
2011-12-09 18:45 ` David Miller
2011-12-09 21:23 ` Ian Campbell
2011-12-10 0:24 ` David Miller
2011-12-11 11:48 ` [PATCH net-next v4] " Laszlo Ersek
2012-01-02 14:50 ` Jan Beulich
2012-01-02 16:54 ` Laszlo Ersek
2012-01-02 17:04 ` Jan Beulich
2012-01-02 17:14 ` Laszlo Ersek [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=4F01E5F9.8060006@redhat.com \
--to=lersek@redhat.com \
--cc=JBeulich@suse.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--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).