From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Erik Stromdahl <erik.stromdahl@gmail.com>
Cc: Akesh M Chacko <akesh.chacko@vvdntech.in>,
Ann Lo <annlo.tech@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Driver support for QCA6174 chip using SDIO interface
Date: Wed, 17 May 2017 09:32:31 +0000 [thread overview]
Message-ID: <87pof76d75.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <933866d5-5ddc-b0d7-98c2-3c7a31ea8276@gmail.com> (Erik Stromdahl's message of "Tue, 16 May 2017 15:13:15 +0200")
Erik Stromdahl <erik.stromdahl@gmail.com> writes:
>> I think we should try to get rest of your patches into mainline as well,
>> even if they are experimental still. Hopefully we get more people
>> helping that way, Adrian already expressed his interest which is very
>> cool and others have been also asking especially SDIO support. And with
>> good luck there are just small fixes needed to SDIO and USB properly
>> working.
>>
> I am actually preparing another RFC round for USB. I think I will split
> my remaining patches in two patchsets: USB and High Latency.
>
> The USB patches will have a few USB specific patches and the HL patches
> will have the high latency stuff that is common between SDIO and USB.
>
> What do you think?
I did take a look at your USB and HL patches earlier but I have already
forgotten what they contained. But at least in principle the split
sounds like a good idea. Just try to keep the size of patchsets
reasonable, a maximum of about a dozen (dependent) patches per set is a
good rule of thumb.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2017-05-17 9:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 14:22 Driver support for QCA6174 chip using SDIO interface Akesh M Chacko
2017-01-27 15:36 ` Valo, Kalle
2017-01-29 21:16 ` Erik Stromdahl
2017-01-31 11:34 ` Akesh M Chacko
2017-02-21 11:26 ` Akesh M Chacko
2017-02-22 20:58 ` Erik Stromdahl
2017-03-01 5:52 ` Akesh M Chacko
2017-03-01 6:25 ` Erik Stromdahl
2017-03-04 4:41 ` Akesh M Chacko
2017-03-09 7:39 ` Valo, Kalle
2017-05-12 0:20 ` Ann Lo
2017-05-12 14:51 ` Erik Stromdahl
2017-05-12 17:30 ` Ann Lo
2017-05-15 17:50 ` Adrian Chadd
2017-05-16 12:59 ` Erik Stromdahl
2017-05-16 7:14 ` Kalle Valo
2017-05-16 13:13 ` Erik Stromdahl
2017-05-17 9:32 ` 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=87pof76d75.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=akesh.chacko@vvdntech.in \
--cc=annlo.tech@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=erik.stromdahl@gmail.com \
/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.