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 net-next 00/14] at86rf230 cleanup
Date: Thu, 24 Apr 2014 19:09:04 +0200 [thread overview]
Message-ID: <1398359358-11085-1-git-send-email-alex.aring@gmail.com> (raw)
Hi,
this is the first patch series to cleanup the at86rf230 driver. Later I want
to implement regmap and a asynchron spi handling for transmit and receiving
frames.
- Alex
Alexander Aring (14):
at86rf230: use irq_get_trigger_type
devicetree: add at86rf230 bindings
at86rf230: remove irq_type in request_irq
at86rf230: use devm_request_irq
at86rf230: use devm_gpio_request_one
at86rf230: add missing MODULE_DEVICE_TABLE
at86rf230: make of_device_id const
at86rf230: add at86rf230_device_id table
at86rf230: remove #ifdef CONFIG_OF
at86rf230: remove unnecessary assign
at86rf230: reset irq line before irq request
at86rf230: remove unnecessary spi_set_drvdata
at86rf230: remove unnecessary state read
at86rf230: remove function for setting irq polarity
.../bindings/net/ieee802154/at86rf230.txt | 23 ++++
drivers/net/ieee802154/at86rf230.c | 133 +++++++--------------
include/linux/spi/at86rf230.h | 14 ---
3 files changed, 65 insertions(+), 105 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/ieee802154/at86rf230.txt
--
1.9.2
next reply other threads:[~2014-04-24 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 17:09 Alexander Aring [this message]
[not found] ` <1398359358-11085-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-24 17:09 ` [PATCH net-next 01/14] at86rf230: use irq_get_trigger_type Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 02/14] devicetree: add at86rf230 bindings Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 03/14] at86rf230: remove irq_type in request_irq Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 04/14] at86rf230: use devm_request_irq Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 05/14] at86rf230: use devm_gpio_request_one Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 06/14] at86rf230: add missing MODULE_DEVICE_TABLE Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 07/14] at86rf230: make of_device_id const Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 08/14] at86rf230: add at86rf230_device_id table Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 09/14] at86rf230: remove #ifdef CONFIG_OF Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 10/14] at86rf230: remove unnecessary assign Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 11/14] at86rf230: reset irq line before irq request Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 12/14] at86rf230: remove unnecessary spi_set_drvdata Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 13/14] at86rf230: remove unnecessary state read Alexander Aring
2014-04-24 17:09 ` [PATCH net-next 14/14] at86rf230: remove function for setting irq polarity Alexander Aring
2014-04-26 16:21 ` [PATCH net-next 00/14] at86rf230 cleanup 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=1398359358-11085-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).