public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: linux-firmware@kernel.org
Cc: linux-kernel@vger.kernel.org, jwboyer@kernel.org,
	rahul.lakkireddy@chelsio.com
Subject: pull request: linux-firmware: update cxgb4 firmware to 1.27.1.0
Date: Wed, 4 Jan 2023 15:39:16 +0530	[thread overview]
Message-ID: <Y7VQTMD97rHTqsBo@chelsio.com> (raw)

Please pull the new Chelsio firmware from the following URL.

  http://git.chelsio.net/pub/git/linux-firmware.git for-upstream

Thanks,
Rahul


The following changes since commit 52261d0329b1a2e414ee394aae3c5ca36283730f:

  Merge https://github.com/pkshih/linux-firmware (2022-12-16 07:10:10 -0500)

are available in the Git repository at:

  http://git.chelsio.net/pub/git/linux-firmware.git for-upstream

for you to fetch changes up to 52e62d6af5c56b82ef49db415b12c8cfe4faf756:

  cxgb4: Update firmware to revision 1.27.1.0 (2023-01-04 09:14:46 +0000)

----------------------------------------------------------------
Rahul Lakkireddy (1):
      cxgb4: Update firmware to revision 1.27.1.0

 WHENCE                                         |  12 ++++++------
 cxgb4/{t4fw-1.27.0.0.bin => t4fw-1.27.1.0.bin} | Bin 570880 -> 570880 bytes
 cxgb4/t5fw-1.27.0.0.bin                        | Bin 677376 -> 0 bytes
 cxgb4/t5fw-1.27.1.0.bin                        | Bin 0 -> 678400 bytes
 cxgb4/{t6fw-1.27.0.0.bin => t6fw-1.27.1.0.bin} | Bin 729600 -> 730112 bytes
 5 files changed, 6 insertions(+), 6 deletions(-)
 rename cxgb4/{t4fw-1.27.0.0.bin => t4fw-1.27.1.0.bin} (73%)
 delete mode 100644 cxgb4/t5fw-1.27.0.0.bin
 create mode 100644 cxgb4/t5fw-1.27.1.0.bin
 rename cxgb4/{t6fw-1.27.0.0.bin => t6fw-1.27.1.0.bin} (54%)

                 reply	other threads:[~2023-01-04 10:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Y7VQTMD97rHTqsBo@chelsio.com \
    --to=rahul.lakkireddy@chelsio.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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