From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de
Subject: Re: [RFC bluetooth-next] atusb: add support for at86rf230
Date: Wed, 27 May 2015 10:47:05 +0200 [thread overview]
Message-ID: <55658489.70604@osg.samsung.com> (raw)
In-Reply-To: <20150527065454.GA712@omega>
Hello.
On 27/05/15 08:54, Alexander Aring wrote:
> 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?
Yes, just send my reviewed-by for it. (You already want acked-by for
this driver for me? I guess I wait until I send a patch to the
maintainers file)
> 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.
I have yet to look at the firmware patches but if Werner already
suggested some changes they should be taken into account. Especially if
this would let us to ifdef hell. :)
I was really happy to see the raven avr stick patches. This will extend
the potential userbase for atusb and ieee802154 quite a bit. Thanks for
working on this.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-05-27 8:47 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
2015-05-27 8:47 ` Stefan Schmidt [this message]
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=55658489.70604@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=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.