public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Shiang Tu <shiang_tu@ralinktech.com>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: [GIT PULL linux-firmware.git] CIS source, Ralink firmware consolidation
Date: Tue, 17 May 2011 13:24:12 +0100	[thread overview]
Message-ID: <1305635052.19966.142.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

The following changes since commit 82273130ddc0af5599b1138b07ebe6ceaabecb72:

  linux-firmware: bnx2: Update firmware and version (2011-05-11 00:27:11 +0100)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-firmware.git master

Ben Hutchings (3):
      Add source and copyright notice for CIS files from pcmcia-cs
      rt2860sta: Use latest firmware for RT3090
      rt2870sta: Use latest firmware for RT3070 and RT3071

 WHENCE                |   39 +++++++++++++++++++++++++++++++++------
 cis/src/3CCFEM556.cis |   22 ++++++++++++++++++++++
 cis/src/3CXEM556.cis  |   22 ++++++++++++++++++++++
 cis/src/COMpad2.cis   |   20 ++++++++++++++++++++
 cis/src/COMpad4.cis   |   14 ++++++++++++++
 cis/src/DP83903.cis   |   24 ++++++++++++++++++++++++
 cis/src/LA-PCM.cis    |   44 ++++++++++++++++++++++++++++++++++++++++++++
 cis/src/MT5634ZLX.cis |   18 ++++++++++++++++++
 cis/src/NE2K.cis      |   10 ++++++++++
 cis/src/PCMLM28.cis   |   37 +++++++++++++++++++++++++++++++++++++
 cis/src/PE-200.cis    |   11 +++++++++++
 cis/src/PE520.cis     |   11 +++++++++++
 cis/src/RS-COM-2P.cis |   14 ++++++++++++++
 cis/src/tamarack.cis  |   17 +++++++++++++++++
 rt3070.bin            |  Bin 4096 -> 10 bytes
 rt3071.bin            |  Bin 4096 -> 4096 bytes
 rt3090.bin            |  Bin 8192 -> 10 bytes
 17 files changed, 297 insertions(+), 6 deletions(-)
 create mode 100644 cis/src/3CCFEM556.cis
 create mode 100644 cis/src/3CXEM556.cis
 create mode 100644 cis/src/COMpad2.cis
 create mode 100644 cis/src/COMpad4.cis
 create mode 100644 cis/src/DP83903.cis
 create mode 100644 cis/src/LA-PCM.cis
 create mode 100644 cis/src/MT5634ZLX.cis
 create mode 100644 cis/src/NE2K.cis
 create mode 100644 cis/src/PCMLM28.cis
 create mode 100644 cis/src/PE-200.cis
 create mode 100644 cis/src/PE520.cis
 create mode 100644 cis/src/RS-COM-2P.cis
 create mode 100644 cis/src/tamarack.cis
 mode change 100644 => 120000 rt3070.bin
 mode change 100644 => 120000 rt3090.bin

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

             reply	other threads:[~2011-05-17 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 12:24 Ben Hutchings [this message]
2011-05-17 12:26 ` [PATCH linux-firmware 1/3] Add source and copyright notice for CIS files from pcmcia-cs Ben Hutchings
2011-05-17 12:26 ` [PATCH firmware 2/3] rt2860sta: Use latest firmware for RT3090 Ben Hutchings
2011-05-17 12:27 ` [PATCH firmware 3/3] rt2870sta: Use latest firmware for RT3070 and RT3071 Ben Hutchings

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=1305635052.19966.142.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shiang_tu@ralinktech.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