linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: linux-firmware@kernel.org
Cc: Connor McAdams <conmanx360@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Additional firmware files for CA0132 HD-audio codec
Date: Wed, 24 Oct 2018 09:37:49 +0200	[thread overview]
Message-ID: <s5hmur3pzg2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181010174923.GA29921@connor-Z97X-Gaming-7>

On Wed, 10 Oct 2018 19:49:23 +0200,
Connor McAdams wrote:
> 
> The following changes since commit c6b6265d718d118e28e1ce8f91769aa886b54c94:
> 
>   Merge tag 'iwlwifi-fw-2018-10-03' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware (2018-10-08 09:23:53 -0400)
> 
> are available in the git repository at:
> 
>   git@github.com:Conmanx360/linux-firmware.git 
> 
> for you to fetch changes up to cd8899323352e772c5989230f35b1c494e0ab196:
> 
>   linux-firmware: Add new firmware for Creative CA0132 HD-Audio Codec (2018-10-09 14:41:12 -0400)
> 
> ----------------------------------------------------------------
> These are additional firmware files for CA0132 based sound cards.
> 
> Creative has given me permission through email to send these to the 
> linux-firmware repository under the same license as the previous ca0132 
> firmware. I asked my contact if they would sign-off on it, but they said 
> to go ahead and submit it and that if there was any issue to contact 
> them. 
> 
> If you need to contact them, or if there's more info needed, let me know
> and I can get see what I can do.
> ----------------------------------------------------------------
> Connor McAdams (1):
>       linux-firmware: Add new firmware for Creative CA0132 HD-Audio Codec
> 
>  WHENCE            |   2 ++
>  ctefx-desktop.bin | Bin 0 -> 655856 bytes
>  ctefx-r3di.bin    | Bin 0 -> 655816 bytes
>  3 files changed, 2 insertions(+)
>  create mode 100644 ctefx-desktop.bin
>  create mode 100644 ctefx-r3di.bin

Please can anyone take a look at this pull request?

It's mandatory for the CA0132-based cards that are now supported
better in the upstream kernel tree.


Thanks!

Takashi

  reply	other threads:[~2018-10-24  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 17:49 [GIT PULL] Additional firmware files for CA0132 HD-audio codec Connor McAdams
2018-10-24  7:37 ` Takashi Iwai [this message]
2018-10-24 13:44   ` Josh Boyer
2018-10-24 16:22     ` Connor McAdams
2018-11-04  5:00       ` Connor McAdams
2018-11-09 19:49         ` Connor McAdams
2018-12-14 12:54           ` 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=s5hmur3pzg2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=conmanx360@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).