From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Erik Stromdahl <erik.stromdahl@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [RFC v2 0/3] ath10k usb support
Date: Thu, 6 Jul 2017 09:17:29 +0000 [thread overview]
Message-ID: <87r2xtexgn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1495312410-9937-1-git-send-email-erik.stromdahl@gmail.com> (Erik Stromdahl's message of "Sat, 20 May 2017 22:33:27 +0200")
Erik Stromdahl <erik.stromdahl@gmail.com> writes:
> This is the 2nd version of the ath10k USB RFC. There are only minor updat=
es
> since last version.
>
> The main difference when compared to the previous RFC is that the
> high latency stuff that is common between USB and SDIO has been moved out
> of this patchset and into another (separate) patchset.
>
> I was actually thinking about squashing all the patches into one, but
> decided not to do so since I wanted usb.h, usb.c and the update Kconfig +
> Makefile in one separate patch.
>
> Perhaps patch 1 and 2 should be squashed?
>
> Erik Stromdahl (3):
> ath10k: various usb related definitions
> ath10k: different fw file names for usb
> ath10k: add initial USB support
This looks good. I'll again do some cosmetic changes and submit v2 as
proper patch. Sorry for taking so long with this.
--=20
Kalle Valo=
prev parent reply other threads:[~2017-07-06 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 20:33 [RFC v2 0/3] ath10k usb support Erik Stromdahl
2017-05-20 20:33 ` [RFC v2 1/3] ath10k: various usb related definitions Erik Stromdahl
2017-05-20 20:33 ` [RFC v2 2/3] ath10k: different fw file names for usb Erik Stromdahl
2017-05-20 20:33 ` [RFC v2 3/3] ath10k: add initial USB support Erik Stromdahl
2017-07-06 9:17 ` Kalle Valo [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=87r2xtexgn.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=erik.stromdahl@gmail.com \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).