linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Sharvari Harisangam <sharvari.harisangam@nxp.com>
Cc: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Cathy Luo <xiaohua.luo@nxp.com>,
	Rakesh Parmar <rakesh.parmar@nxp.com>,
	Mayur Arakere <mayur.arakere@nxp.com>
Subject: Re: pull-request mwifiex-firmware 2021-05-19
Date: Wed, 19 May 2021 11:23:44 -0700	[thread overview]
Message-ID: <CA+ASDXM4u=98XmyAH9=iXQGT8mP-z3WKs9vN=Ms20xXmJyKnWw@mail.gmail.com> (raw)
Message-ID: <20210519182344.cLtegmJLnF6WKlyVBnC-eLey3yEOgyPu_nRJ_hT3WXk@z> (raw)
In-Reply-To: <DB7PR04MB45387F399B5963BD92C57CA3FC2B9@DB7PR04MB4538.eurprd04.prod.outlook.com>

On Wed, May 19, 2021 at 7:45 AM Sharvari Harisangam
<sharvari.harisangam@nxp.com> wrote:
>
> The following changes since commit 2a0a062e79b5fe9007e57c0fcd285e683e22373e:
>
>   linux-firmware: update NXP SDSD-8997 firmware image (2020-08-03 06:51:36 +0530)
>
> are available in the git repository at:
>
>   https://github.com/NXP/mwifiex-firmware.git
>
> for you to fetch changes up to db190ade4569c542cd257a9334f8f8956372f7b3:
>
>   linux-firmware: update NXP PCIE-USB-8997 firmware image (2021-05-19 12:57:21 -0700)
>
> ----------------------------------------------------------------
> Sharvari Harisangam (1):
>       linux-firmware: update NXP PCIE-USB-8997 firmware image
>
>  WHENCE                       |   2 ++
>  nxp/pcieusb8997_combo_v4.bin | Bin 0 -> 638992 bytes
>  2 files changed, 2 insertions(+)
>  create mode 100644 nxp/pcieusb8997_combo_v4.bin

I appreciate that NXP now owns what was formerly known as Marvell
WiFi, but the driver still only recognizes "mrvl/" naming, not "nxp/".
Did you actually test that this does anything useful? Or are you
planning on submitting driver patches to use the new path? That seems
like unnecessary churn to me, and you should just use the old path.

Brian

  reply	other threads:[~2021-05-19 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 14:44 pull-request mwifiex-firmware 2021-05-19 Sharvari Harisangam
2021-05-19 18:23 ` Brian Norris [this message]
2021-05-19 18:23   ` Brian Norris
2021-05-20 23:41     ` Pali Rohár

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='CA+ASDXM4u=98XmyAH9=iXQGT8mP-z3WKs9vN=Ms20xXmJyKnWw@mail.gmail.com' \
    --to=briannorris@chromium.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mayur.arakere@nxp.com \
    --cc=rakesh.parmar@nxp.com \
    --cc=sharvari.harisangam@nxp.com \
    --cc=xiaohua.luo@nxp.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).