From: WANG Cong <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [patch net-next-2.6 5/6] bonding: get rid of IFF_SLAVE_INACTIVE netdev->priv_flag
Date: Mon, 14 Mar 2011 05:29:35 +0000 (UTC) [thread overview]
Message-ID: <ilk93u$ant$1@dough.gmane.org> (raw)
In-Reply-To: 1299935679-18135-6-git-send-email-jpirko@redhat.com
On Sat, 12 Mar 2011 14:14:38 +0100, Jiri Pirko wrote:
> Since bond-related code was moved from net/core/dev.c into bonding,
> IFF_SLAVE_INACTIVE is no longer needed. Replace is with flag "inactive"
> stored in slave structure
>
Good work, Jiri!
IFF_ flags are valuable and are going to be exhausted, moving
these slave-specific flags to struct slave is indeed good.
Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
Thanks.
next prev parent reply other threads:[~2011-03-14 5:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 13:14 [patch net-next-2.6 0/6] mostly bonding cleanups (partial repost) Jiri Pirko
2011-03-12 13:14 ` [patch net-next-2.6 1/6] af_packet: use skb->skb_iif instead of orig_dev->ifindex Jiri Pirko
2011-03-13 23:52 ` Changli Gao
2011-03-14 6:54 ` Jiri Pirko
2011-03-14 6:59 ` Changli Gao
2011-03-14 7:43 ` Jiri Pirko
2011-03-14 15:10 ` Changli Gao
2011-03-12 13:14 ` [patch net-next-2.6 2/6] bonding: register slave pointer for rx_handler Jiri Pirko
2011-03-16 19:52 ` David Miller
2011-03-12 13:14 ` [patch net-next-2.6 3/6] net: get rid of multiple bond-related netdevice->priv_flags Jiri Pirko
2011-03-16 18:45 ` [patch net-next-2.6 3/6 v2] " Jiri Pirko
2011-03-16 19:52 ` David Miller
2011-03-12 13:14 ` [patch net-next-2.6 4/6] bonding: wrap slave state work Jiri Pirko
2011-03-16 19:52 ` David Miller
2011-03-12 13:14 ` [patch net-next-2.6 5/6] bonding: get rid of IFF_SLAVE_INACTIVE netdev->priv_flag Jiri Pirko
2011-03-14 5:29 ` WANG Cong [this message]
2011-03-16 18:46 ` [patch net-next-2.6 5/6 v2] " Jiri Pirko
2011-03-16 19:52 ` David Miller
2011-03-12 13:14 ` [patch net-next-2.6 6/6] net: introduce rx_handler results and logic around that Jiri Pirko
2011-03-12 13:24 ` Nicolas de Pesloüan
2011-03-12 13:25 ` Nicolas de Pesloüan
2011-03-12 13:36 ` Jiri Pirko
2011-03-16 19:53 ` David Miller
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='ilk93u$ant$1@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--cc=netdev@vger.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).