From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
James Chapman <jchapman@katalix.com>,
Alexander Duyck <aduyck@mirantis.com>,
Vlad Yasevich <vyasevich@gmail.com>,
Florian Westphal <fw@strlen.de>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Daniel Borkmann <daniel@iogearbox.net>,
stephen hemminger <stephen@networkplumber.org>,
Tom Herbert <tom@herbertland.com>,
linux-sctp@vger.kernel.org, Antonio Quartulli <a@unstable.cc>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Mugunthan V N <mugunthanvnm@ti.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
Eric Dumazet <edumazet
Subject: [PATCH 0/8] net: use IS_ENABLED() instead of checking for built-in or module
Date: Fri, 9 Sep 2016 08:43:12 -0400 [thread overview]
Message-ID: <1473425000-9782-1-git-send-email-javier@osg.samsung.com> (raw)
Hello David,
This trivial series replace the open coding to check for a Kconfig symbol
being built-in or module, with IS_ENABLED() macro that does exactly that.
Using the macro makes the code more readable by helping abstract away some
of the Kconfig built-in and module enable details.
Best regards,
Javier
Javier Martinez Canillas (8):
appletalk: use IS_ENABLED() instead of checking for built-in or module
lec: use IS_ENABLED() instead of checking for built-in or module
net: use IS_ENABLED() instead of checking for built-in or module
ipv4: use IS_ENABLED() instead of checking for built-in or module
l2tp: use IS_ENABLED() instead of checking for built-in or module
net: sched: use IS_ENABLED() instead of checking for built-in or
module
sctp: use IS_ENABLED() instead of checking for built-in or module
xfrm: use IS_ENABLED() instead of checking for built-in or module
net/appletalk/ddp.c | 2 +-
net/atm/lec.c | 12 ++++++------
net/core/dev.c | 3 +--
net/ipv4/ip_output.c | 2 +-
net/l2tp/l2tp_core.h | 2 +-
net/l2tp/l2tp_eth.c | 4 ++--
net/l2tp/l2tp_ppp.c | 4 ++--
net/sched/cls_flow.c | 6 +++---
net/sctp/auth.c | 2 +-
net/xfrm/xfrm_algo.c | 2 +-
10 files changed, 19 insertions(+), 20 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-09 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 12:43 Javier Martinez Canillas [this message]
2016-09-09 12:43 ` [PATCH 1/8] appletalk: use IS_ENABLED() instead of checking for built-in or module Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 2/8] lec: " Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 3/8] net: " Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 4/8] ipv4: " Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 5/8] l2tp: " Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 6/8] net: sched: " Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 7/8] sctp: " Javier Martinez Canillas
2016-09-09 16:43 ` Neil Horman
2016-09-09 12:43 ` [PATCH 8/8] xfrm: " Javier Martinez Canillas
2016-09-11 4:19 ` [PATCH 0/8] net: " 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=1473425000-9782-1-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=a@unstable.cc \
--cc=acme@ghostprotocols.net \
--cc=aduyck@mirantis.com \
--cc=daniel@iogearbox.net \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=jchapman@katalix.com \
--cc=jhs@mojatatu.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=nikolay@cumulusnetworks.com \
--cc=steffen.klassert@secunet.com \
--cc=stephen@networkplumber.org \
--cc=tom@herbertland.com \
--cc=vyasevich@gmail.com \
--cc=yoshfuji@linux-ipv6.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).