From: "Valo, Kalle" <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 v3 0/8] ath10k sdio support
Date: Sun, 19 Feb 2017 13:59:48 +0000 [thread overview]
Message-ID: <8737fagu28.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <877f4ngii5.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Sun, 19 Feb 2017 01:57:06 +0200")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Erik Stromdahl <erik.stromdahl@gmail.com> writes:
>
>> I was actually about to email you about this.
>>
>> I have made a few more updates to the sdio code so I think it would be
>> best if I could submit a new series of patches based on this code (v4).
>>
>> Then you can tweak it (v5).
>>
>> It is only minor updates to the HIF layer (added QCA9377 support) and
>> a setup of some pll registers.
>
> Ok, that sounds good. I'll wait for v4.
Forgot to mention can you run ath10k-check before submitting them, it
shows few problems:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/codingstyle#checking_code
But if you wonder what this is about it's checkpatch warning about camel
case (doesn't like the lower case x character):
drivers/net/wireless/ath/ath10k/sdio.h:68: <ATH10K_SDIO_DRIVE_DTSx_TYPE_C>
I guess I have a bug in the script when it parses checkpatch output.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-02-19 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 21:26 [RFC v3 0/8] ath10k sdio support Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 1/8] ath10k: htc: made static function public Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 2/8] ath10k: htc: rx trailer lookahead support Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 3/8] ath10k: htc: move htc ctrl ep connect to htc_init Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 4/8] ath10k: htc: refactorization Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 5/8] ath10k: various sdio related definitions Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 6/8] ath10k: sdio support Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 7/8] ath10k: sdio get target info Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 8/8] ath10k: htc: ready_ext msg support Erik Stromdahl
2017-01-23 11:08 ` [RFC v3 0/8] ath10k sdio support Valo, Kalle
2017-02-18 13:40 ` Valo, Kalle
2017-02-18 22:05 ` Erik Stromdahl
2017-02-18 23:57 ` Valo, Kalle
2017-02-19 13:59 ` Valo, Kalle [this message]
2017-02-19 16:21 ` Erik Stromdahl
2017-02-19 16:33 ` Valo, Kalle
[not found] <7b204d34-b791-ea78-cf4e-90e8fe1b79fb@gmail.com>
2017-02-19 13:52 ` Erik Stromdahl
2017-02-19 14:05 ` Valo, Kalle
2017-02-19 16:30 ` Erik Stromdahl
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=8737fagu28.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