From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, Stefan Schmidt <stefan@osg.samsung.com>
Subject: Re: [RFC bluetooth-next] atusb: add support for at86rf230
Date: Wed, 27 May 2015 08:54:59 +0200 [thread overview]
Message-ID: <20150527065454.GA712@omega> (raw)
In-Reply-To: <1432471383-5029-1-git-send-email-alex.aring@gmail.com>
Stefan,
On Sun, May 24, 2015 at 02:43:03PM +0200, Alexander Aring wrote:
> This patch adds support for the at86rf230 version check which is used
> by the rzusb stick.
>
is it okay to apply this patch for mainline for now? Then it's only a
question to make _better_ patches for the atusb firmware. Werner told me
that I should remove the a lot of ifdefs or we landing in a ifdef hell
which is like a well known IoT-OS and that's true. Was a dirty hack.
If it's okay then I will send a patch again.
- Alex
next prev parent reply other threads:[~2015-05-27 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 12:43 [RFC bluetooth-next] atusb: add support for at86rf230 Alexander Aring
2015-05-27 6:54 ` Alexander Aring [this message]
2015-05-27 8:47 ` Stefan Schmidt
2015-05-27 8:42 ` Stefan Schmidt
2015-05-27 11:46 ` Alexander Aring
2015-05-27 11:49 ` 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=20150527065454.GA712@omega \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@osg.samsung.com \
/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