From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH bluetooth-next 4/6] ieee802154: sysfs: add missing include
Date: Sun, 2 Nov 2014 21:43:04 +0100 [thread overview]
Message-ID: <1414960986-7051-5-git-send-email-alex.aring@gmail.com> (raw)
In-Reply-To: <1414960986-7051-1-git-send-email-alex.aring@gmail.com>
Running make C=2 occurs in warnings:
symbol 'wpan_phy_class' was not declared. Should it be static?
symbol 'wpan_phy_sysfs_init' was not declared. Should it be static?
symbol 'wpan_phy_sysfs_exit' wasnot declared. Should it be static?
This patch adds a missing include "sysfs.h" to solve these warnings.
Signed-off-by: Alexander Aring <alex.aring@gmail.com>
Reported-by: Marcel Holtmann <marcel@holtmann.org>
---
net/ieee802154/sysfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ieee802154/sysfs.c b/net/ieee802154/sysfs.c
index c6e0380..8819998 100644
--- a/net/ieee802154/sysfs.c
+++ b/net/ieee802154/sysfs.c
@@ -18,6 +18,7 @@
#include <net/cfg802154.h>
#include "core.h"
+#include "sysfs.h"
static inline struct cfg802154_registered_device *
dev_to_rdev(struct device *dev)
--
2.1.3
next prev parent reply other threads:[~2014-11-02 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 20:43 [PATCH bluetooth-next 0/6] ieee802154: solve make C=2 warnings Alexander Aring
2014-11-02 20:43 ` [PATCH bluetooth-next 1/6] ieee802154: add missing ULL definition Alexander Aring
2014-11-02 20:43 ` [PATCH bluetooth-next 2/6] ieee802154: fix byteorder issues Alexander Aring
2014-11-02 20:43 ` [PATCH bluetooth-next 3/6] mac802154: " Alexander Aring
2014-11-02 20:43 ` Alexander Aring [this message]
2014-11-02 20:43 ` [PATCH bluetooth-next 5/6] mac802154: cfg: add missing include Alexander Aring
2014-11-02 20:43 ` [PATCH bluetooth-next 6/6] ieee802154: remove unnecessary functions Alexander Aring
2014-11-02 20:52 ` [PATCH bluetooth-next 0/6] ieee802154: solve make C=2 warnings Marcel Holtmann
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=1414960986-7051-5-git-send-email-alex.aring@gmail.com \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@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