From: Erik Stromdahl <erik.stromdahl@gmail.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: "Hsu, Ryan" <ryanhsu@qca.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v3 0/8] ath10k sdio support
Date: Sun, 19 Feb 2017 17:30:36 +0100 [thread overview]
Message-ID: <c004b837-ccb6-f87b-ce49-bd685f9272c1@gmail.com> (raw)
In-Reply-To: <87y3x2ff7y.fsf@kamboji.qca.qualcomm.com>
On 2017-02-19 15:05, Valo, Kalle wrote:
> Erik Stromdahl <erik.stromdahl@gmail.com> writes:
>
>> I just noticed that Ryan Hsu submitted two patches containing similar
>> functionality to what I have in my tree on github. They have not been
>> integrated in the ath master yet, but they have been added to master-pending.
>>
>> Below are the commits I am talking about
>>
>> bc1054a15be3c962c83aa22476a3e9c1266da792 ath10k: improve the firmware
>> download time for QCA9377
>> db5af2a25bd8c1410ec4456d1d4f4e6ded2649ca ath10k: improve the firmware
>> download time for QCA6174
>>
>> Since some of my patches overlap with these I think it would be best if
>> I add these to my tree and rewrite my patches.
>>
>> If they haven't made it into master before I submit my updated patch series
>> I will include them in my set.
>>
>> Is this OK?
>>
>> If they will be added to master soon there is no issue since I will of course
>> rebase to the latest ath-YYYYMMDDHHmm before I submit anything.
>
> That's ok, just mention this in the cover letter.
>
> Even better is that if you can use master-pending from ath.git as the
> baseline (compared to the master branch normally recommended), Ryan's
> patches are there now. That way you don't need to apply anything extra
> to your tree. But I'm hoping to apply Ryan's patches soon anyway.
>
Ok, I'll make it so.
WARNING: multiple messages have this Message-ID (diff)
From: Erik Stromdahl <erik.stromdahl@gmail.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"Hsu, Ryan" <ryanhsu@qca.qualcomm.com>
Subject: Re: [RFC v3 0/8] ath10k sdio support
Date: Sun, 19 Feb 2017 17:30:36 +0100 [thread overview]
Message-ID: <c004b837-ccb6-f87b-ce49-bd685f9272c1@gmail.com> (raw)
In-Reply-To: <87y3x2ff7y.fsf@kamboji.qca.qualcomm.com>
On 2017-02-19 15:05, Valo, Kalle wrote:
> Erik Stromdahl <erik.stromdahl@gmail.com> writes:
>
>> I just noticed that Ryan Hsu submitted two patches containing similar
>> functionality to what I have in my tree on github. They have not been
>> integrated in the ath master yet, but they have been added to master-pending.
>>
>> Below are the commits I am talking about
>>
>> bc1054a15be3c962c83aa22476a3e9c1266da792 ath10k: improve the firmware
>> download time for QCA9377
>> db5af2a25bd8c1410ec4456d1d4f4e6ded2649ca ath10k: improve the firmware
>> download time for QCA6174
>>
>> Since some of my patches overlap with these I think it would be best if
>> I add these to my tree and rewrite my patches.
>>
>> If they haven't made it into master before I submit my updated patch series
>> I will include them in my set.
>>
>> Is this OK?
>>
>> If they will be added to master soon there is no issue since I will of course
>> rebase to the latest ath-YYYYMMDDHHmm before I submit anything.
>
> That's ok, just mention this in the cover letter.
>
> Even better is that if you can use master-pending from ath.git as the
> baseline (compared to the master branch normally recommended), Ryan's
> patches are there now. That way you don't need to apply anything extra
> to your tree. But I'm hoping to apply Ryan's patches soon anyway.
>
Ok, I'll make it so.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-02-19 16:30 UTC|newest]
Thread overview: 39+ 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 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 1/8] ath10k: htc: made static function public Erik Stromdahl
2017-01-13 21:26 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 2/8] ath10k: htc: rx trailer lookahead support Erik Stromdahl
2017-01-13 21:26 ` 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 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 4/8] ath10k: htc: refactorization Erik Stromdahl
2017-01-13 21:26 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 5/8] ath10k: various sdio related definitions Erik Stromdahl
2017-01-13 21:26 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 6/8] ath10k: sdio support Erik Stromdahl
2017-01-13 21:26 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 7/8] ath10k: sdio get target info Erik Stromdahl
2017-01-13 21:26 ` Erik Stromdahl
2017-01-13 21:26 ` [RFC v3 8/8] ath10k: htc: ready_ext msg support Erik Stromdahl
2017-01-13 21:26 ` Erik Stromdahl
2017-01-23 11:08 ` [RFC v3 0/8] ath10k sdio support Valo, Kalle
2017-01-23 11:08 ` Valo, Kalle
2017-02-18 13:40 ` Valo, Kalle
2017-02-18 13:40 ` Valo, Kalle
2017-02-18 22:05 ` Erik Stromdahl
2017-02-18 22:05 ` Erik Stromdahl
2017-02-18 23:57 ` Valo, Kalle
2017-02-18 23:57 ` Valo, Kalle
2017-02-19 13:19 ` Erik Stromdahl
2017-02-19 13:52 ` Erik Stromdahl
2017-02-19 13:52 ` Erik Stromdahl
2017-02-19 14:05 ` Valo, Kalle
2017-02-19 14:05 ` Valo, Kalle
2017-02-19 16:30 ` Erik Stromdahl [this message]
2017-02-19 16:30 ` Erik Stromdahl
2017-02-19 13:59 ` Valo, Kalle
2017-02-19 13:59 ` Valo, Kalle
2017-02-19 16:21 ` Erik Stromdahl
2017-02-19 16:21 ` Erik Stromdahl
2017-02-19 16:33 ` Valo, Kalle
2017-02-19 16:33 ` Valo, Kalle
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=c004b837-ccb6-f87b-ce49-bd685f9272c1@gmail.com \
--to=erik.stromdahl@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ryanhsu@qca.qualcomm.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.