From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Eyal Reizer <eyalr@ti.com>, Guy Mishol <guym@ti.com>,
Maital Hahn <maitalm@ti.com>,
Maxim Altshul <maxim.altshul@ti.com>,
Shahar Patury <shaharp@ti.com>,
linux-wireless@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/5] wlcore: sdio: Populate config firmware data
Date: Wed, 14 Sep 2016 20:08:49 +0300 [thread overview]
Message-ID: <87intycsta.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160913215043.29454-4-tony@atomide.com> (Tony Lindgren's message of "Tue, 13 Sep 2016 14:50:41 -0700")
Tony Lindgren <tony@atomide.com> writes:
> Configure the config firmware names and make it available
> in platform data.
>
> Let's also fix the order of the struct wilink_family_data
> while at it.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
> drivers/net/wireless/ti/wlcore/spi.c | 42 ++++++++++++++++++++----------------
> 1 file changed, 24 insertions(+), 18 deletions(-)
I think the title should be:
wlcore: spi: Populate config firmware data
I can fix that during commit.
--
Kalle Valo
next prev parent reply other threads:[~2016-09-14 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 21:50 [PATCH 0/5] Fix wlcore config firwmare annoyances Tony Lindgren
2016-09-13 21:50 ` [PATCH 1/5] wlcore: Prepare family to fix nvs file handling Tony Lindgren
2016-09-13 21:50 ` [PATCH 2/5] wlcore: sdio: Populate config firmware data Tony Lindgren
2016-09-13 21:50 ` [PATCH 3/5] " Tony Lindgren
2016-09-14 17:08 ` Kalle Valo [this message]
2016-09-14 17:13 ` Tony Lindgren
2016-09-13 21:50 ` [PATCH 4/5] wlcore: Fix config firmware loading issues Tony Lindgren
2016-09-13 21:50 ` [PATCH 5/5] wlcore: wl18xx: Use chip specific configuration firmware Tony Lindgren
2016-09-17 15:24 ` [PATCH 0/5] Fix wlcore config firwmare annoyances Kalle Valo
2016-09-17 15:37 ` Tony Lindgren
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=87intycsta.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=eyalr@ti.com \
--cc=guym@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maitalm@ti.com \
--cc=maxim.altshul@ti.com \
--cc=shaharp@ti.com \
--cc=tony@atomide.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 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).