From: Stefan Schmidt <stefan@osg.samsung.com>
To: Josef Filzmaier <j.filzmaier@gmx.at>, linux-wpan@vger.kernel.org
Subject: Re: [PATCH bluetooth-next 1/1] atusb: Driver support for Busware HUL USB dongle
Date: Thu, 14 Sep 2017 15:33:07 +0200 [thread overview]
Message-ID: <c4424060-51aa-ae5f-d040-99a0a713e079@osg.samsung.com> (raw)
In-Reply-To: <7924089.9ctYqWRe3X@hella-laptop>
Hello.
On 09/14/2017 02:32 PM, Josef Filzmaier wrote:
>> Hello.
>
> Hello!
>
>> Could you add a ieee802154: before the atusb: in the subject? That makes
>> it clearer to what area of the kernel it belongs.
>
> Yes, i did just resubmit my patch.
>
>> scripts/checkpatch.pl --strict $PATCHNAME
>
> I did not know this script existed, otherwise i would have checked earlier. :)
We need to have _some_ secrets, right? ;)
If you want to learn more about kernel development (you learned and
adapted quickly) dig through the Documentation folder. Its a mix of
technical but also development docs.
>> Both patches have been applied to the atusb firmware repo.
>> I also added a tiny section in the README how to get the firmware on the
>> device.
>
>> Thanks a lot for your efforts on this!
>
> Thank you very much for your support!
Let us know how the development on top of this device and the upcoming
hardware with a SPI attached transceiver goes. Hearing stories how the
stack can be used and what shortcomings it has will help us to improve.
regards
Stefan Schmidt
prev parent reply other threads:[~2017-09-14 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 23:18 [PATCH bluetooth-next 0/1] *** Support for Busware HUL stick *** Josef Filzmaier
2017-09-01 23:18 ` [PATCH bluetooth-next 1/1] atusb: Driver support for Busware HUL USB dongle Josef Filzmaier
2017-09-14 9:40 ` Stefan Schmidt
2017-09-14 12:32 ` Josef Filzmaier
2017-09-14 13:33 ` Stefan Schmidt [this message]
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=c4424060-51aa-ae5f-d040-99a0a713e079@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=j.filzmaier@gmx.at \
--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.