netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: javier@osg.samsung.com
Cc: linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru,
	nikolay@cumulusnetworks.com, jchapman@katalix.com,
	aduyck@mirantis.com, vyasevich@gmail.com, fw@strlen.de,
	acme@ghostprotocols.net, yoshfuji@linux-ipv6.org,
	daniel@iogearbox.net, stephen@networkplumber.org,
	tom@herbertland.com, linux-sctp@vger.kernel.org, a@unstable.cc,
	jhs@mojatatu.com, herbert@gondor.apana.org.au,
	mugunthanvnm@ti.com, steffen.klassert@secunet.com,
	edumazet@google.com, felipe.balbi@linux.intel.com,
	netdev@vger.kernel.org, jiri@mellanox.com, nhorman@tuxdriver.com,
	jarod@redhat.com, kaber@trash.net, pabeni@redhat.com,
	jmorris@namei.org
Subject: Re: [PATCH 0/8] net: use IS_ENABLED() instead of checking for built-in or module
Date: Sat, 10 Sep 2016 21:19:28 -0700 (PDT)	[thread overview]
Message-ID: <20160910.211928.1782362547702903708.davem@davemloft.net> (raw)
In-Reply-To: <1473425000-9782-1-git-send-email-javier@osg.samsung.com>

From: Javier Martinez Canillas <javier@osg.samsung.com>
Date: Fri,  9 Sep 2016 08:43:12 -0400

> 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.

Series applied, thanks.

      parent reply	other threads:[~2016-09-11  4:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 12:43 [PATCH 0/8] net: use IS_ENABLED() instead of checking for built-in or module Javier Martinez Canillas
2016-09-09 12:43 ` [PATCH 1/8] appletalk: " 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 ` 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=20160910.211928.1782362547702903708.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=a@unstable.cc \
    --cc=acme@ghostprotocols.net \
    --cc=aduyck@mirantis.com \
    --cc=daniel@iogearbox.net \
    --cc=edumazet@google.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=fw@strlen.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarod@redhat.com \
    --cc=javier@osg.samsung.com \
    --cc=jchapman@katalix.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@mellanox.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=nikolay@cumulusnetworks.com \
    --cc=pabeni@redhat.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).