From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org, Vikas Patel <vikpatel@codeaurora.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k: avoid consecutive OTP download to reduce boot time
Date: Fri, 14 Feb 2020 11:16:29 +0530 [thread overview]
Message-ID: <0a3ff5df5e16e2657f76214d1448d0ad@codeaurora.org> (raw)
In-Reply-To: <87pnei7exs.fsf@codeaurora.org>
On 2020-02-13 19:43, Kalle Valo wrote:
> Maharaja Kennadyrajan <mkenna@codeaurora.org> writes:
>
>> On 2020-01-07 11:53, Maharaja Kennadyrajan wrote:
>>
>> [Maha]: Please ignore/drop this duplicate patch as I sent it already.
>> Regret for inconvenience caused.
>
> Are you sure I should drop this? In the first patch I think you forgot
> to CC linux-wireless and that's why I didn't see it. But this second
> patch was CCed to linux-wireless and I see it on patchwork. So my plan
> is to put this back to my queue, please let me know if I have
> misunderstood.
[Maha]: Hi Kalle, I sent the same patch twice. So I asked to ignore one
duplicate patch.
You can pick up this patch to put it in your queue and please ignore the
duplicate patch.
WARNING: multiple messages have this Message-ID (diff)
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Vikas Patel <vikpatel@codeaurora.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: avoid consecutive OTP download to reduce boot time
Date: Fri, 14 Feb 2020 11:16:29 +0530 [thread overview]
Message-ID: <0a3ff5df5e16e2657f76214d1448d0ad@codeaurora.org> (raw)
In-Reply-To: <87pnei7exs.fsf@codeaurora.org>
On 2020-02-13 19:43, Kalle Valo wrote:
> Maharaja Kennadyrajan <mkenna@codeaurora.org> writes:
>
>> On 2020-01-07 11:53, Maharaja Kennadyrajan wrote:
>>
>> [Maha]: Please ignore/drop this duplicate patch as I sent it already.
>> Regret for inconvenience caused.
>
> Are you sure I should drop this? In the first patch I think you forgot
> to CC linux-wireless and that's why I didn't see it. But this second
> patch was CCed to linux-wireless and I see it on patchwork. So my plan
> is to put this back to my queue, please let me know if I have
> misunderstood.
[Maha]: Hi Kalle, I sent the same patch twice. So I asked to ignore one
duplicate patch.
You can pick up this patch to put it in your queue and please ignore the
duplicate patch.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-02-14 5:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 6:23 [PATCH] ath10k: avoid consecutive OTP download to reduce boot time Maharaja Kennadyrajan
2020-01-07 6:23 ` Maharaja Kennadyrajan
2020-01-07 7:00 ` Maharaja Kennadyrajan
2020-01-07 7:00 ` Maharaja Kennadyrajan
2020-02-13 14:13 ` Kalle Valo
2020-02-13 14:13 ` Kalle Valo
2020-02-14 5:46 ` Maharaja Kennadyrajan [this message]
2020-02-14 5:46 ` Maharaja Kennadyrajan
2020-03-11 16:31 ` Kalle Valo
2020-03-11 16:31 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2020-01-06 10:51 Maharaja Kennadyrajan
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=0a3ff5df5e16e2657f76214d1448d0ad@codeaurora.org \
--to=mkenna@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vikpatel@codeaurora.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.