From: Alexander Aring <alex.aring@gmail.com>
To: alex.bluesman.smirnov@gmail.com
Cc: dbaryshkov@gmail.com, linux-zigbee-devel@lists.sourceforge.net,
netdev@vger.kernel.org, Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH 1/2] at86rf230: add help and 212 to Kconfig menu entry
Date: Tue, 4 Mar 2014 11:22:29 +0100 [thread overview]
Message-ID: <1393928550-31949-1-git-send-email-alex.aring@gmail.com> (raw)
Since commit e035b8addc544c2b4de2f8b0326ba7939abd9541 we support at86rf212
aswell.
Signed-off-by: Alexander Aring <alex.aring@gmail.com>
---
drivers/net/ieee802154/Kconfig | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ieee802154/Kconfig b/drivers/net/ieee802154/Kconfig
index 08ae465..807ad1f 100644
--- a/drivers/net/ieee802154/Kconfig
+++ b/drivers/net/ieee802154/Kconfig
@@ -32,8 +32,14 @@ config IEEE802154_FAKELB
config IEEE802154_AT86RF230
depends on IEEE802154_DRIVERS && MAC802154
- tristate "AT86RF230/231 transceiver driver"
+ tristate "AT86RF230/231/212 transceiver driver"
depends on SPI
+ ---help---
+ Say Y here to enable the at86rf230/231/212 SPI 802.15.4 wireless
+ controller.
+
+ This driver can also be built as a module. To do so, say M here.
+ the module will be called 'at86rf230'.
config IEEE802154_MRF24J40
tristate "Microchip MRF24J40 transceiver driver"
--
1.9.0
next reply other threads:[~2014-03-04 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 10:22 Alexander Aring [this message]
2014-03-04 10:22 ` [PATCH 2/2] ieee802154: fix whitespace issues in Kconfig Alexander Aring
2014-03-04 18:13 ` [PATCH 1/2] at86rf230: add help and 212 to Kconfig menu entry Sergei Shtylyov
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=1393928550-31949-1-git-send-email-alex.aring@gmail.com \
--to=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--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).