public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ding Tianhong <dingtianhong@huawei•com>
To: Jay Vosburgh <fubar@us•ibm.com>,
	Andy Gospodarek <andy@greyhouse•net>,
	"David S. Miller" <davem@davemloft•net>,
	Veaceslav Falico <vfalico@redhat•com>,
	Netdev <netdev@vger•kernel.org>,
	Scott Feldman <sfeldma@cumulusnetworks•com>
Subject: [PATCH net-next v2 0/3] bonding: add lp_interval option support and simplify the code
Date: Sat, 21 Dec 2013 14:39:47 +0800	[thread overview]
Message-ID: <52B537B3.3060504@huawei.com> (raw)

The option lp_interval could only be set by sysfs, so add support for loading module.
and update the Documentation/networking/bonding.txt for this option.

Use micro BOND_NO_USE_ARP to simplify the code for mode check.

v2: according to the networking coding style, the patch 01/03 need to cleanup the
    style problem, thanks scott for his advice. The bond_check_param() have too
    many duplicated code with bond sysfs, so I think when scott finish the bond_option_xxx_set(),
    the bond_check_param() should be modify to use the bond_option_xxx_set() function
    to simplify the code.

Ding Tianhong (3):
  bonding: add option lp_interval for loading module
  bonding: ust micro BOND_NO_USE_ARP to simplify the mode check
  bonding: update Documentation/networking/bonding.txt for option
    lp_interval

 Documentation/networking/bonding.txt | 10 ++++++++++
 drivers/net/bonding/bond_main.c      | 29 +++++++++++++++--------------
 2 files changed, 25 insertions(+), 14 deletions(-)

-- 
1.8.0

             reply	other threads:[~2013-12-21  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21  6:39 Ding Tianhong [this message]
2013-12-31  5:40 ` [PATCH net-next v2 0/3] bonding: add lp_interval option support and simplify the code 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=52B537B3.3060504@huawei.com \
    --to=dingtianhong@huawei$(echo .)com \
    --cc=andy@greyhouse$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=fubar@us$(echo .)ibm.com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sfeldma@cumulusnetworks$(echo .)com \
    --cc=vfalico@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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