All of lore.kernel.org
 help / color / mirror / Atom feed
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/5] at86rf230: cleanups
Date: Mon, 15 Dec 2014 00:20:27 +0100	[thread overview]
Message-ID: <1418599232-6267-1-git-send-email-alex.aring@gmail.com> (raw)

This patch series contains various cleanups for the at86rf230.
Except patch 3/5 which contains a fix for a rarely error handling.
Because this error handling is very rarely and should only happens
if something is wrong with the spi controller, it's okay to fix it
in next.

- Alex

Alexander Aring (5):
  at86rf230: remove if branch
  at86rf230: make at86rf230_async_error inline
  at86rf230: fix context pointer handling
  at86rf230: cleanup check on trac status
  at86rf230: remove unnecessary assign

 drivers/net/ieee802154/at86rf230.c | 18 ++++++------------
 1 file changed, 6 insertions(+), 12 deletions(-)

-- 
2.1.3


             reply	other threads:[~2014-12-14 23:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 23:20 Alexander Aring [this message]
2014-12-14 23:20 ` [PATCH bluetooth-next 1/5] at86rf230: remove if branch Alexander Aring
2014-12-15  8:29   ` Stefan Schmidt
2014-12-15  8:45     ` Alexander Aring
2014-12-15  8:49       ` Alexander Aring
2014-12-14 23:20 ` [PATCH bluetooth-next 2/5] at86rf230: make at86rf230_async_error inline Alexander Aring
2014-12-15  8:29   ` Stefan Schmidt
2014-12-15  8:39     ` Alexander Aring
2014-12-15  9:01       ` Stefan Schmidt
2014-12-15  9:04         ` Alexander Aring
2014-12-14 23:20 ` [PATCH bluetooth-next 3/5] at86rf230: fix context pointer handling Alexander Aring
2014-12-15  8:29   ` Stefan Schmidt
2014-12-14 23:20 ` [PATCH bluetooth-next 4/5] at86rf230: cleanup check on trac status Alexander Aring
2014-12-15  8:29   ` Stefan Schmidt
2014-12-14 23:20 ` [PATCH bluetooth-next 5/5] at86rf230: remove unnecessary assign Alexander Aring
2014-12-15  8:29   ` Stefan Schmidt

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=1418599232-6267-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.