From: David Miller <davem@davemloft.net>
To: jpirko@redhat.com
Cc: netdev@vger.kernel.org, fubar@us.ibm.com,
bonding-devel@lists.sourceforge.net,
shemminger@linux-foundation.org, kaber@trash.net
Subject: Re: [net-next-2.6 PATCH 0/3] bonding: refuse to change bond type if it's used V3
Date: Thu, 18 Mar 2010 20:05:14 -0700 (PDT) [thread overview]
Message-ID: <20100318.200514.48485837.davem@davemloft.net> (raw)
In-Reply-To: <20100310202804.GC2834@psychotron.redhat.com>
From: Jiri Pirko <jpirko@redhat.com>
Date: Wed, 10 Mar 2010 21:28:04 +0100
> v2->v3:
> -changed defines name to NETDEV_[PRE/POST]_TYPE_CHANGE
> -added bits for vlan and macvlan
>
> Reworked version of patch/patchset. This time I use netdevice notifier as
> Stephen suggested. Changed the name of the original ones (NETDEV_BONDING_*TYPE)
> to be more general and reused them.
This looks really nice, applied thanks Jiri.
I know a lot of people who would have noticed this and
just said "not my problem" and gone on to work on something
else. Instead you stopped and fixed it, and this is very
much appreciated.
Thanks again!
prev parent reply other threads:[~2010-03-19 3:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 20:28 [net-next-2.6 PATCH 0/3] bonding: refuse to change bond type if it's used V3 Jiri Pirko
2010-03-10 20:28 ` [net-next-2.6 PATCH 1/3] net: rename notifier defines for netdev type change Jiri Pirko
2010-03-10 20:29 ` [net-next-2.6 PATCH 2/3] bonding: check return value of nofitier when changing type Jiri Pirko
2010-03-10 22:47 ` [Bonding-devel] " Stephen Hemminger
2010-03-11 7:59 ` Jiri Pirko
2010-03-11 9:53 ` Jiri Pirko
2010-03-10 20:30 ` [net-next-2.6 PATCH 3/3] net: forbid underlaying devices to change its type Jiri Pirko
2010-03-10 21:04 ` Jay Vosburgh
2010-03-10 21:17 ` Jiri Pirko
2010-03-19 3:05 ` 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=20100318.200514.48485837.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=jpirko@redhat.com \
--cc=kaber@trash.net \
--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).