From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "Raja, Tamizh Chelvam" <c_traja@qti.qualcomm.com>,
"tamizhchelvam@codeaurora.org" <tamizhchelvam@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCHv3 1/3] ath10k: move firmware_swap_code_seg_info to ath10k_fw_file
Date: Wed, 31 Aug 2016 07:04:42 +0000 [thread overview]
Message-ID: <87poop4dx2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGRGNgWd-5ef5bxOkthpfH1hjqO4HJuWuBA=jNRAr=geQDH1zA@mail.gmail.com> (Julian Calaby's message of "Mon, 4 Jul 2016 10:49:55 +1000")
Julian Calaby <julian.calaby@gmail.com> writes:
> Hi Tamizh,
>
> On Fri, Jul 1, 2016 at 5:06 PM, <c_traja@qti.qualcomm.com> wrote:
>> From: Tamizh chelvam <c_traja@qti.qualcomm.com>
>>
>> Preparation to make use of firmware_swap_code_seg_info for UTF binary.
>>
>> Signed-off-by: Tamizh chelvam <c_traja@qti.qualcomm.com>
>> ---
>> drivers/net/wireless/ath/ath10k/core.c | 6 +++---
>> drivers/net/wireless/ath/ath10k/core.h | 6 ++----
>> drivers/net/wireless/ath/ath10k/swap.c | 26 ++++++++++++++-----------=
-
>> drivers/net/wireless/ath/ath10k/swap.h | 11 ++++++++---
>> 4 files changed, 27 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wirele=
ss/ath/ath10k/core.h
>> index 3da18c9..e69e7e7 100644
>> --- a/drivers/net/wireless/ath/ath10k/core.h
>> +++ b/drivers/net/wireless/ath/ath10k/core.h
>> @@ -654,6 +654,8 @@ struct ath10k_fw_file {
>>
>> const void *codeswap_data;
>> size_t codeswap_len;
>> + /* FIXME: add a comment */
>> + struct ath10k_swap_code_seg_info *firmware_swap_code_seg_info;
>
> Why not just add a comment? Adding FIXMEs makes the patch look incomplete=
to me.
Actually I'm here to blame, I asked Tamizh to add the fixme so I can add
a proper comment. I did it now:
--- a/drivers/net/wireless/ath/ath10k/core.h
+++ b/drivers/net/wireless/ath/ath10k/core.h
@@ -663,7 +663,14 @@ struct ath10k_fw_file {
=20
const void *codeswap_data;
size_t codeswap_len;
- /* FIXME: add a comment */
+
+ /* The original idea of struct ath10k_fw_file was that it only
+ * contains struct firmware and pointers to various parts (actual
+ * firmware binary, otp, metadata etc) of the file. This seg_info
+ * is actually created separate but as this is used similarly as
+ * the other firmware components it's more convenient to have it
+ * here.
+ */
struct ath10k_swap_code_seg_info *firmware_swap_code_seg_info;
};
--=20
Kalle Valo=
next prev parent reply other threads:[~2016-08-31 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 7:06 [PATCHv3 1/3] ath10k: move firmware_swap_code_seg_info to ath10k_fw_file c_traja
2016-07-04 0:49 ` Julian Calaby
2016-08-31 7:04 ` Valo, Kalle [this message]
2016-08-31 7:19 ` [PATCHv3, " Kalle Valo
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=87poop4dx2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.com \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tamizhchelvam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox