From: David Miller <davem@davemloft.net>
To: Ian.Campbell@citrix.com
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org,
Jeremy.Fitzhardinge@citrix.com, stable@kernel.org
Subject: Re: [PATCH 0/2] fixes to arp_notify for virtual machine migration use case
Date: Mon, 31 May 2010 00:32:47 -0700 (PDT) [thread overview]
Message-ID: <20100531.003247.245412006.davem@davemloft.net> (raw)
In-Reply-To: <1274868492.24218.7350.camel@zakaz.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
Date: Wed, 26 May 2010 11:08:12 +0100
> Ian Campbell (3):
> arp_notify: document that a gratuitous ARP request is sent when this option is enabled
> arp_notify: allow drivers to explicitly request a notification event.
> xen: netfront: explicitly generate arp_notify event after migration.
Applied to net-next-2.6, there was a new bonding notifier added meanwhile
and I changed the number of your new notifier to fix the conflict.
prev parent reply other threads:[~2010-05-31 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 13:39 [PATCH 0/2] fixes to arp_notify for virtual machine migration use case Ian Campbell
2010-05-12 13:40 ` [PATCH] arp_notify: generate broadcast ARP reply not request Ian Campbell
2010-05-12 13:40 ` [PATCH] arp_notify: generate arp_notify event on NETDEV_CHANGE too Ian Campbell
2010-05-24 6:37 ` [PATCH 0/2] fixes to arp_notify for virtual machine migration use case David Miller
2010-05-25 9:20 ` Ian Campbell
2010-05-26 6:08 ` David Miller
2010-05-26 10:08 ` Ian Campbell
2010-05-26 10:09 ` [PATCH 1/3] arp_notify: document that a gratuitous ARP request is sent when this option is enabled Ian Campbell
2010-05-26 10:09 ` [PATCH 2/3] arp_notify: allow drivers to explicitly request a notification event Ian Campbell
2010-05-26 10:09 ` [PATCH 3/3] xen: netfront: explicitly generate arp_notify event after migration Ian Campbell
2010-05-31 7:32 ` 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=20100531.003247.245412006.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ian.Campbell@citrix.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=stable@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).