From: Josh Boyer <jwboyer@kernel.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>,
Rakesh Parmar <rakesh.parmar@nxp.com>,
Cathy Luo <xiaohua.luo@nxp.com>
Subject: Re: pull-request mwifiex-firmware 2021-07-05
Date: Fri, 16 Jul 2021 07:59:52 -0400 [thread overview]
Message-ID: <CA+5PVA5on7+CRtEV7tThPxgucwt3W9i-tEXm4cgH-AmMB-Jrtg@mail.gmail.com> (raw)
In-Reply-To: <DB7PR04MB453855B0D6C41923BCB0922EFC1C9@DB7PR04MB4538.eurprd04.prod.outlook.com>
On Mon, Jul 5, 2021 at 3:40 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 312ca028298317d2babb54080c056408cdb9448b:
>
> linux-firmware: update NXP 8897/8997 firmware images (2021-07-05 05:42:09 -0700)
>
> ----------------------------------------------------------------
> Sharvari Harisangam (1):
> linux-firmware: update NXP 8897/8997 firmware images
I cherry-picked that commit and pushed it out.
That NXP tree seems to have some divergent history from the main
linux-firmware repo, so PRs get conflicts in things like the WHENCE
file. I have no idea what is going on there, but if you could base
your PRs on the main linux-firmware repo in the future that would be
helpful.
josh
>
> mrvl/pcieusb8997_combo_v4.bin | Bin 634228 -> 638992 bytes
> mrvl/sd8897_uapsta.bin | Bin 701072 -> 717068 bytes
> 2 files changed, 0 insertions(+), 0 deletions(-)
> ~
next prev parent reply other threads:[~2021-07-16 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 7:40 pull-request mwifiex-firmware 2021-07-05 Sharvari Harisangam
2021-07-16 11:59 ` Josh Boyer [this message]
2021-07-22 23:00 ` 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+5PVA5on7+CRtEV7tThPxgucwt3W9i-tEXm4cgH-AmMB-Jrtg@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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).