From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: alex.bluesman.smirnov@gmail.com, dbaryshkov@gmail.com,
linux-zigbee-devel@lists.sourceforge.net, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
backports@vger.kernel.org, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [PATCH 1/3] 6lowpan: add helper to get 6lowpan namespace
Date: Tue, 22 Apr 2014 11:44:46 +0200 [thread overview]
Message-ID: <1398159886.4211.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1397784176-15809-2-git-send-email-mcgrof@do-not-panic.com> (sfid-20140418_032412_117495_4585013B)
On Thu, 2014-04-17 at 18:22 -0700, Luis R. Rodriguez wrote:
> +#if IS_ENABLED(CONFIG_IEEE802154_6LOWPAN)
> [...]
> +#else
> +static inline struct netns_ieee802154_lowpan *
> +net_ieee802154_lowpan(struct net *net)
> +{
> + return NULL;
> +}
> +#endif
Why would that be needed? If nobody compiles 802.15.4 then it seems
nothing should reference it?
johannes
next prev parent reply other threads:[~2014-04-22 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 1:22 [PATCH 0/3] 6lowpan: few changes to help with backports Luis R. Rodriguez
[not found] ` <1397784176-15809-1-git-send-email-mcgrof-3uybbJdB1yH774rrrx3eTA@public.gmane.org>
2014-04-18 1:22 ` [PATCH 1/3] 6lowpan: add helper to get 6lowpan namespace Luis R. Rodriguez
2014-04-22 9:44 ` Johannes Berg [this message]
2014-04-22 9:53 ` Alexander Aring
2014-04-22 17:58 ` Luis R. Rodriguez
2014-04-22 18:45 ` Johannes Berg
[not found] ` <1398192315.4211.25.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2014-04-22 18:49 ` Alexander Aring
2014-04-22 19:09 ` Luis R. Rodriguez
2014-04-22 19:03 ` Luis R. Rodriguez
2014-04-18 1:22 ` [PATCH 2/3] 6lowpan: make lowpan_cb static Luis R. Rodriguez
2014-04-18 1:22 ` [PATCH 3/3] 6lowpan: include net/net_namespace.h on 6lowpan namepsace header Luis R. Rodriguez
2014-04-20 22:21 ` [PATCH 0/3] 6lowpan: few changes to help with backports 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=1398159886.4211.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=backports@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.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).