From: Hariprasad S <hariprasad@chelsio.com>
To: <linux-firmware@kernel.org>
Cc: <ben@decadent.org.uk>, <dwmw2@infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: pull request: linux-firmware: update cxgb4 firmware
Date: Fri, 27 Jun 2014 17:39:11 +0530 [thread overview]
Message-ID: <20140627120910.GA2406@hariprasad-pc> (raw)
Hi,
Can you please pull from the following URL?
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
The following changes since commit 7f388b4885cf64d6b7833612052d20d4197af96f:
Ben Hutchings (1):
Move the s5p-mfc firmware out of its subdirectory
are available in the git repository at:
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
Hariprasad Shenai (1):
cxgb4: Update firmware to revision 1.11.27.0
LICENCE.chelsio_firmware | 2 +-
WHENCE | 8 ++++----
cxgb4/t4fw-1.11.27.0.bin | Bin 0 -> 512512 bytes
cxgb4/t4fw-1.9.23.0.bin | Bin 486912 -> 0 bytes
cxgb4/t4fw.bin | 2 +-
cxgb4/t5fw-1.11.27.0.bin | Bin 0 -> 513024 bytes
cxgb4/t5fw-1.9.23.0.bin | Bin 481280 -> 0 bytes
cxgb4/t5fw.bin | 2 +-
8 files changed, 7 insertions(+), 7 deletions(-)
create mode 100644 cxgb4/t4fw-1.11.27.0.bin
delete mode 100644 cxgb4/t4fw-1.9.23.0.bin
create mode 100644 cxgb4/t5fw-1.11.27.0.bin
delete mode 100644 cxgb4/t5fw-1.9.23.0.bin
next reply other threads:[~2014-06-27 12:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 12:09 Hariprasad S [this message]
2014-08-04 17:48 ` pull request: linux-firmware: update cxgb4 firmware Kyle McMartin
2014-08-06 6:36 ` Hariprasad S
2014-08-06 12:28 ` Kyle McMartin
-- strict thread matches above, loose matches on Subject: below --
2019-04-09 9:59 pull request: Linux-firmware: Update " Vishal Kulkarni
2019-04-09 10:41 ` Josh Boyer
[not found] <MWHPR12MB13437FB2B95FE8F4B3456B3ACB4B0@MWHPR12MB1343.namprd12.prod.outlook.com>
2019-03-14 12:24 ` pull request: linux-firmware: update " Josh Boyer
[not found] <BN7PR12MB2660B14B55248BDC8BAF800AA0BB0@BN7PR12MB2660.namprd12.prod.outlook.com>
2019-01-14 15:28 ` Josh Boyer
2018-11-02 11:12 Ganesh Goudar
2018-12-14 12:53 ` Josh Boyer
2018-07-07 3:15 Ganesh Goudar
2018-07-13 14:22 ` Josh Boyer
2018-04-25 15:06 Ganesh Goudar
2018-05-01 12:10 ` Josh Boyer
2018-05-02 6:21 ` Ganesh Goudar
2018-03-27 20:57 Ganesh Goudar
2018-03-30 0:30 ` Josh Boyer
2018-03-15 13:29 Ganesh Goudar
2018-03-27 10:40 ` Arjun V
2018-03-27 12:56 ` Josh Boyer
2018-01-17 11:01 Ganesh Goudar
2018-01-19 12:07 ` Josh Boyer
2017-09-27 15:24 Ganesh Goudar
2017-10-09 16:50 ` Ben Hutchings
2017-05-28 11:59 Ganesh Goudar
2017-05-30 19:24 ` Kyle McMartin
2017-04-26 14:36 Ganesh Goudar
2017-05-11 16:38 ` Kyle McMartin
2017-02-27 14:31 Ganesh Goudar
2017-02-27 19:33 ` Kyle McMartin
2017-02-27 4:10 Ganesh Goudar
2017-01-04 12:49 Ganesh Goudar
2017-01-13 15:07 ` Kyle McMartin
2015-03-25 8:46 Hariprasad S
2015-03-30 14:19 ` Kyle McMartin
2014-10-17 18:33 Hariprasad S
2014-12-01 11:28 ` Hariprasad S
2013-12-15 19:32 Hariprasad S
2013-12-16 0:07 ` Ben Hutchings
2013-12-16 19:34 ` Hariprasad S
2013-11-27 8:15 Hariprasad S
2013-12-15 18:05 ` Ben Hutchings
2013-11-14 9:00 Hariprasad S
2013-11-27 7:38 ` Hariprasad S
2012-06-15 0:09 Divy Le Ray
2012-06-15 2:11 ` Ben Hutchings
2011-08-29 18:02 Divy Le Ray
2011-09-15 12:30 ` Neil Horman
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=20140627120910.GA2406@hariprasad-pc \
--to=hariprasad@chelsio.com \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.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