From: "Raju Rangoju" <rajur@chelsio.com>
To: Josh Boyer <jwboyer@kernel.org>,
"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ramaraju Yelavarthy <ramaraju@chelsio.com>,
"Raju Rangoju" <rajur@chelsio.com>
Subject: pull request: linux-firmware: update cxgb4 firmware to 1.25.6.0
Date: Mon, 24 May 2021 11:00:42 +0000 [thread overview]
Message-ID: <BN9PR12MB53218D9345EF839962E1E4C9BC269@BN9PR12MB5321.namprd12.prod.outlook.com> (raw)
Hi,
Can you please pull the new firmware from the following URL?
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
Thanks,
Raju
The following changes since commit f8462923ed8fc874f770b8c6dfad49d39b381f14:
nvidia: fix symlinks for tu104/tu106 acr unload firmware (2021-05-18 11:03:08 -0400)
are available in the git repository at:
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
for you to fetch changes up to 0c8946d82f059f90199f4926ab55033d8aa9c920:
cxgb4: Update firmware to revision 1.25.6.0 (2021-05-24 00:51:20 -0700)
----------------------------------------------------------------
Raju Rangoju (1):
cxgb4: Update firmware to revision 1.25.6.0
WHENCE | 12 ++++++------
cxgb4/{t4fw-1.25.4.0.bin => t4fw-1.25.6.0.bin} | Bin 569856 -> 570368 bytes
cxgb4/{t5fw-1.25.4.0.bin => t5fw-1.25.6.0.bin} | Bin 675328 -> 675840 bytes
cxgb4/t6fw-1.25.4.0.bin | Bin 728064 -> 0 bytes
cxgb4/t6fw-1.25.6.0.bin | Bin 0 -> 730112 bytes
5 files changed, 6 insertions(+), 6 deletions(-)
rename cxgb4/{t4fw-1.25.4.0.bin => t4fw-1.25.6.0.bin} (75%)
rename cxgb4/{t5fw-1.25.4.0.bin => t5fw-1.25.6.0.bin} (78%)
delete mode 100644 cxgb4/t6fw-1.25.4.0.bin
create mode 100644 cxgb4/t6fw-1.25.6.0.bin
next reply other threads:[~2021-05-24 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 11:00 Raju Rangoju [this message]
2021-05-24 11:00 ` pull request: linux-firmware: update cxgb4 firmware to 1.25.6.0 Raju Rangoju
2021-06-09 12:00 ` Josh Boyer
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=BN9PR12MB53218D9345EF839962E1E4C9BC269@BN9PR12MB5321.namprd12.prod.outlook.com \
--to=rajur@chelsio.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ramaraju@chelsio.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).