From: Veaceslav Falico <vfalico@gmail.com>
To: netdev@vger.kernel.org
Cc: Jay Vosburgh <j.vosburgh@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
Veaceslav Falico <vfalico@gmail.com>
Subject: [PATCH net-next 0/2] bonding: add its own Kconfig
Date: Tue, 15 Jul 2014 12:15:39 +0200 [thread overview]
Message-ID: <1405419341-31510-1-git-send-email-vfalico@gmail.com> (raw)
Currently to change some built-in defaults it's necessary to change the
code, and to maintain these patches on each update.
Create a bonding's Kconfig to make it possible to configure them at build
time.
CC: Jay Vosburgh <j.vosburgh@gmail.com>
CC: Andy Gospodarek <andy@greyhouse.net>
CC: "David S. Miller" <davem@davemloft.net>
CC: netdev@vger.kernel.org
Signed-off-by: Veaceslav Falico <vfalico@gmail.com>
---
drivers/net/Kconfig | 18 +-----------------
drivers/net/bonding/Kconfig | 33 +++++++++++++++++++++++++++++++++
drivers/net/bonding/bonding.h | 6 +++---
3 files changed, 37 insertions(+), 20 deletions(-)
next reply other threads:[~2014-07-15 10:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 10:15 Veaceslav Falico [this message]
2014-07-15 10:15 ` [PATCH net-next 1/2] bonding: create its own Kconfig Veaceslav Falico
2014-07-15 10:15 ` [PATCH net-next 2/2] bonding: make hard-coded defines configurable at build Veaceslav Falico
2014-07-15 15:48 ` Alexei Starovoitov
2014-07-15 16:18 ` Veaceslav Falico
2014-07-15 16:45 ` Alexei Starovoitov
2014-07-15 17:11 ` Veaceslav Falico
2014-07-15 17:33 ` Alexei Starovoitov
2014-07-15 17:53 ` Veaceslav Falico
2014-07-15 18:55 ` Alexei Starovoitov
2014-07-15 19:18 ` Veaceslav Falico
2014-07-16 1:01 ` David Miller
2014-07-15 17:11 ` Sergei Shtylyov
2014-07-16 1:10 ` [PATCH net-next 0/2] bonding: add its own Kconfig David Miller
2014-07-16 7:20 ` Veaceslav Falico
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=1405419341-31510-1-git-send-email-vfalico@gmail.com \
--to=vfalico@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=j.vosburgh@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).