netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	"Jeremy Fitzhardinge" <jeremy@goop.org>,
	"David S. Miller" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: arp_notify: allow drivers to explicitly request a notification event.
Date: Wed, 11 Aug 2010 21:16:20 +0100	[thread overview]
Message-ID: <1281557780.7349.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20100811193959.GA9470@kroah.com>

On Wed, 2010-08-11 at 20:39 +0100, Greg KH wrote:
> On Wed, Aug 11, 2010 at 12:39:25PM -0700, Greg KH wrote:

> > > index 540703b..22c2abb 100644
> > > --- a/include/linux/notifier.h
> > > +++ b/include/linux/notifier.h
> > > @@ -210,6 +210,7 @@ static inline int notifier_to_errno(int ret)
> > >  #define NETDEV_POST_INIT	0x0010
> > >  #define NETDEV_UNREGISTER_BATCH 0x0011
> > >  #define NETDEV_BONDING_DESLAVE  0x0012
> > > +#define NETDEV_NOTIFY_PEERS	0x0012
> > 
> > Are you sure that you can duplicate this value?
> 
> Oh nevermind, David already fixed this up with commit
> 38117d1495e587fbb10d6e55733139a27893cef5

David did mention that he fixed up a clash at the timebut I hadn't
realised it was a separate checkin, thanks for figuring it out.

> I'll go queue that up for -stable as well :)

Cool, thanks.

Ian.



      reply	other threads:[~2010-08-11 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 19:39 arp_notify: allow drivers to explicitly request a notification event Greg KH
2010-08-11 19:39 ` Greg KH
2010-08-11 20:16   ` Ian Campbell [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=1281557780.7349.1.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=jeremy@goop.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).