From: Kalle Valo <kvalo@codeaurora.org>
To: "Reizer\, Eyal" <eyalr@ti.com>
Cc: "\,Tony Lindgren" <tony@atomide.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wlcore: add missing nvs file name info for wilink8
Date: Mon, 03 Jul 2017 14:29:32 +0300 [thread overview]
Message-ID: <87y3s5kbc3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8665E2433BC68541A24DFFCA87B70F5B363E1A3D@DFRE01.ent.ti.com> (Eyal Reizer's message of "Mon, 3 Jul 2017 10:54:43 +0000")
"Reizer, Eyal" <eyalr@ti.com> writes:
> When working with wl18xx the nvs file is used for defining an alternate
> mac address and override the default mac address that is stored inside
> the wl18xx chip.
> update the structure field with the same default nvs file name that has
> been used in the past, otherwise userspace backward compatibility is
> broken when upgrading from older kernels, as the alternate mac address
> would not be read from the nvs that is already present in the file system
> (lib/firmware/ti-connectivity/wl1271-nvs.bin) causing mac address change
> of the wlan interface.
>
> Signed-off-by: Eyal Reizer <eyalr@ti.com>
Should we also cc stable? And a Fixes line would be nice.
--
Kalle Valo
next prev parent reply other threads:[~2017-07-03 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 10:54 [PATCH] wlcore: add missing nvs file name info for wilink8 Reizer, Eyal
2017-07-03 10:54 ` Reizer, Eyal
2017-07-03 11:29 ` Kalle Valo [this message]
2017-07-04 8:17 ` Tony Lindgren
2017-07-04 8:46 ` Reizer, Eyal
2017-07-04 8:46 ` Reizer, Eyal
2017-07-05 8:06 ` Tony Lindgren
2017-07-05 8:28 ` Sebastian Reichel
2017-07-06 6:26 ` Tony Lindgren
2017-07-20 7:38 ` Reizer, Eyal
2017-07-20 7:38 ` Reizer, Eyal
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=87y3s5kbc3.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=eyalr@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 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.