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 0/6] at86rf230: improvements and cleanups
Date: Sun, 1 Mar 2015 21:55:27 +0100 [thread overview]
Message-ID: <1425243333-8344-1-git-send-email-alex.aring@gmail.com> (raw)
Hi,
this series contains some improvements in transmit handling which insert
a retry mode for going into STATE_TX_ON instead of turning into this state
with forcing after the first try. This series contains also some improvements
/cleanups which squash some multiple dereferencing and don't overwrite a
memory space always with the same number.
- Alex
Alexander Aring (6):
at86rf230: add transmit retry support
at86rf230: cleanup and squash stack variable
at86rf230: refactor receive handling
at86rf230: remove multiple dereferencing for irq
at86rf230: remove multiple dereferencing for ctx
at86rf230: restore trx len when needed
drivers/net/ieee802154/at86rf230.c | 117 +++++++++++++++++++++----------------
1 file changed, 67 insertions(+), 50 deletions(-)
--
2.3.0
next reply other threads:[~2015-03-01 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 20:55 Alexander Aring [this message]
2015-03-01 20:55 ` [PATCH bluetooth-next 1/6] at86rf230: add transmit retry support Alexander Aring
2015-03-01 20:55 ` [PATCH bluetooth-next 2/6] at86rf230: cleanup and squash stack variable Alexander Aring
2015-03-01 20:55 ` [PATCH bluetooth-next 3/6] at86rf230: refactor receive handling Alexander Aring
2015-03-01 20:55 ` [PATCH bluetooth-next 4/6] at86rf230: remove multiple dereferencing for irq Alexander Aring
2015-03-01 20:55 ` [PATCH bluetooth-next 5/6] at86rf230: remove multiple dereferencing for ctx Alexander Aring
2015-03-01 20:55 ` [PATCH bluetooth-next 6/6] at86rf230: restore trx len when needed Alexander Aring
2015-03-03 1:17 ` [PATCH bluetooth-next 0/6] at86rf230: improvements and cleanups 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=1425243333-8344-1-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