From: Stefan Schmidt <stefan@osg.samsung.com>
To: Werner Almesberger <werner@almesberger.net>
Cc: Alexander Aring <alex.aring@gmail.com>,
linux-wpan@vger.kernel.org, kernel@pengutronix.de,
marcel@holtmann.org, Richard Sharpe <realrichardsharpe@gmail.com>
Subject: Re: [PATCH bluetooth-next 21/34] ieee802154: add support for atusb transceiver
Date: Tue, 19 May 2015 16:21:12 +0200 [thread overview]
Message-ID: <555B46D8.5080807@osg.samsung.com> (raw)
In-Reply-To: <20150519134520.GF10959@ws>
Hello.
On 19/05/15 15:45, Werner Almesberger wrote:
> Stefan Schmidt wrote:
>> Werner, is this something you would do? Making a release of the
>> firmware? Or should Alexander or myself look into this?
> It would be great if you or Alexander could take care of that. I'm
> not doing much with 802.15.4 these days, so for me that would be a
> distraction at best, and - without a setup in active use - testing
> would be awkward.
>
OK, I think I can handle this during the week. Will post a file here for
further testing.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-05-19 14:21 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 19:44 [PATCH bluetooth-next 00/34] ieee802154: capabilities, atusb support and fakelb rework Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 01/34] nl802154: cleanup invalid argument handling Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 02/34] ieee802154: move validation check out of softmac Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 03/34] ieee802154: change transmit power to s32 Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 04/34] ieee802154: change transmit power to mbm Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 05/34] ieee802154: change cca ed level " Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 06/34] ieee802154: introduce wpan_phy_supported Alexander Aring
2015-05-18 10:19 ` Varka Bhadram
2015-05-17 19:44 ` [PATCH bluetooth-next 07/34] ieee802154: add several phy supported handling Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 08/34] mac802154: check for really changes Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 09/34] mac802154: remove check if operation is supported Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 10/34] cfg802154: introduce wpan phy flags Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 11/34] ieee802154: add iftypes capability Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 12/34] at86rf230: set cca_modes supported flags Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 13/34] at86rf230: rework tx power support Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 14/34] at86rf230: rework tx cca energy detection level Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 15/34] at86rf230: add cca ed level reset value Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 16/34] at86rf230: add reset states of tx power level Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 17/34] nl802154: add support for dump phy capabilities Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 18/34] mac802154: fakelb: Fix potential NULL pointer dereference Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 19/34] at86rf230: fix callback for aret handling Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 20/34] mac802154: tx: allow xmit complete from hard irq Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 21/34] ieee802154: add support for atusb transceiver Alexander Aring
2015-05-19 10:49 ` Stefan Schmidt
2015-05-19 11:52 ` Alexander Aring
2015-05-19 13:22 ` Stefan Schmidt
2015-05-19 13:45 ` Werner Almesberger
2015-05-19 14:21 ` Stefan Schmidt [this message]
2015-05-20 8:45 ` Stefan Schmidt
2015-05-20 9:03 ` Alexander Aring
2015-05-20 9:08 ` Stefan Schmidt
2015-05-17 19:44 ` [PATCH bluetooth-next 22/34] fakelb: creating two virtual phys per default Alexander Aring
2015-05-17 19:44 ` [PATCH bluetooth-next 23/34] fakelb: use list_for_each_entry_safe Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 24/34] fakelb: rename fakelb_dev_priv to fakelb_phy Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 25/34] fakelb: don't deliver when one phy Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 26/34] fakelb: declare rwlock static Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 27/34] fakelb: declare fakelb list static Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 28/34] fakelb: move lock out of iteration Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 29/34] fakelb: introduce fakelb ifup phys list Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 30/34] fakelb: use own channel and page attributes Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 31/34] fakelb: add virtual phy reset defaults Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 32/34] fakelb: remove fakelb_hw_deliver Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 33/34] fakelb: add support for async xmit handling Alexander Aring
2015-05-17 19:45 ` [PATCH bluetooth-next 34/34] fakelb: cleanup code Alexander Aring
2015-05-19 9:50 ` [PATCH bluetooth-next 00/34] ieee802154: capabilities, atusb support and fakelb rework 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=555B46D8.5080807@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=realrichardsharpe@gmail.com \
--cc=werner@almesberger.net \
/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