From: Hariprasad S <hariprasad@chelsio.com>
To: <ben@decadent.org.uk>, <dwmw2@infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <felix@chelsio.com>
Subject: pull request: linux-firmware: update cxgb4 firmware
Date: Mon, 16 Dec 2013 01:02:21 +0530 [thread overview]
Message-ID: <20131215193220.GA7536@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 7d0c7a8cfd78388d90cc784a185b19dcbdbce824:
Ben Hutchings (1):
Merge branch 'wilink4' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/linux-firmware
are available in the git repository at:
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
Hariprasad Shenai (1):
cxgb4: Updated T4 firmware, add T5 firmware
WHENCE | 8 +++++---
cxgb4/t4fw-1.6.2.0.bin | Bin 431616 -> 0 bytes
cxgb4/t4fw-1.9.23.0.bin | Bin 0 -> 486912 bytes
cxgb4/t4fw.bin | 2 +-
cxgb4/t5fw-1.9.23.0.bin | Bin 0 -> 481280 bytes
cxgb4/t5fw.bin | 1 +
6 files changed, 7 insertions(+), 4 deletions(-)
delete mode 100644 cxgb4/t4fw-1.6.2.0.bin
create mode 100644 cxgb4/t4fw-1.9.23.0.bin
create mode 100644 cxgb4/t5fw-1.9.23.0.bin
create mode 120000 cxgb4/t5fw.bin
Thanks,
Hariprasad Shenai
next reply other threads:[~2013-12-15 19:32 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 19:32 Hariprasad S [this message]
2013-12-16 0:07 ` pull request: linux-firmware: update cxgb4 firmware Ben Hutchings
2013-12-16 19:34 ` Hariprasad S
[not found] ` <20131216014537.GA8008@hariprasad-pc>
2013-12-19 10:31 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2020-04-16 11:36 pull request: Linux-firmware: Update " Vishal Kulkarni
2020-04-17 15:16 ` Josh Boyer
2019-04-09 9:59 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
2014-06-27 12:09 Hariprasad S
2014-08-04 17:48 ` Kyle McMartin
2014-08-06 6:36 ` Hariprasad S
2014-08-06 12:28 ` Kyle McMartin
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=20131215193220.GA7536@hariprasad-pc \
--to=hariprasad@chelsio.com \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=felix@chelsio.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.