From: Sven Eckelmann <sven.eckelmann@open-mesh.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] ath10k: Add board data download from target
Date: Mon, 06 Jun 2016 12:10:17 +0200 [thread overview]
Message-ID: <3343488.td5VS5T2AQ@bentobox> (raw)
In-Reply-To: <87porxt78w.fsf@kamboji.qca.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
On Saturday 04 June 2016 13:26:39 you wrote:
[...]
> Looking at this again I noticed that we issue this warning even if
> EEPROM is not supported, which I think is wrong. I fixed this in the
> pending branch, the diff is below.
>
> I also renamed target_board_data to cal_eeprom because, at least to my
> understanding, the eeprom actually contains the real calibration data,
> not the board data file.
>
> Please review so that I didn't break anything.
Thanks for the changes. Looks good to me.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-06 10:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 14:40 [PATCH 0/2] ath10k: Add support for QCA9887 Sven Eckelmann
2016-05-20 14:41 ` [PATCH 1/2] ath10k: add QCA9887 chipset support Sven Eckelmann
2016-05-23 6:22 ` Mohammed Shafi Shajakhan
2016-05-23 6:52 ` Mohammed Shafi Shajakhan
2016-06-04 13:21 ` Valo, Kalle
2016-06-07 11:29 ` [1/2] " Kalle Valo
2016-05-20 14:41 ` [PATCH 2/2] ath10k: Add board data download from target Sven Eckelmann
2016-06-04 13:26 ` Valo, Kalle
2016-06-06 10:10 ` Sven Eckelmann [this message]
2016-05-26 17:32 ` [PATCH 0/2] ath10k: Add support for QCA9887 Valo, Kalle
2016-05-27 8:46 ` Sven Eckelmann
2016-05-27 12:44 ` Valo, Kalle
2016-05-30 11:12 ` Sven Eckelmann
2016-06-07 14:50 ` Mohammed Shafi Shajakhan
2016-06-07 16:54 ` Sven Eckelmann
2016-06-07 17:11 ` Mohammed Shafi Shajakhan
2016-06-08 12:43 ` Mohammed Shafi Shajakhan
2016-06-09 5:06 ` Mohammed Shafi Shajakhan
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=3343488.td5VS5T2AQ@bentobox \
--to=sven.eckelmann@open-mesh.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).