linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Connor McAdams <conmanx360@gmail.com>
To: jwboyer@kernel.org
Cc: Takashi Iwai <tiwai@suse.de>,
	linux-firmware@kernel.org, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Additional firmware files for CA0132 HD-audio codec
Date: Fri, 9 Nov 2018 14:49:22 -0500	[thread overview]
Message-ID: <CAM8Agx2KYOZK97J7yiM9JvNF1bxiAKNtA_YDegtLMVAYiWKEXQ@mail.gmail.com> (raw)
In-Reply-To: <CAM8Agx1VK3QNV52RmiSsrD8042oFRKZg-w6WFa7SPfebVa4hQQ@mail.gmail.com>

Okay... So, my contact at Creative gave me an email as the 'sign-off
party' for firmware submission. As far as I'm aware, sign-offs also
need names attached, correct? So I'll ask for that. However, they
still want me to send it.

Will that be okay? Would you be more comfortable if I get you in
contact with someone at Creative,Josh?

I apologize for being kind of difficult, I'm doing what I can. Let me
know what I need to do, and I'll do my best.

Thanks,
Connor.
On Sun, Nov 4, 2018 at 1:00 AM Connor McAdams <conmanx360@gmail.com> wrote:
>
> Okay, just got a response from the guy at Creative. He said they'll
> try to sort it out this week. Just a heads up. :)
> On Wed, Oct 24, 2018 at 12:22 PM Connor McAdams <conmanx360@gmail.com> wrote:
> >
> > Understood. I will see what I can do. I already had them contact
> > Takashi, but I will ask if they're willing to give a sign-off. If
> > they're having trouble, is it okay to have them contact you Josh?
> >
> > Let me know.
> > On Wed, Oct 24, 2018 at 9:44 AM Josh Boyer <jwboyer@kernel.org> wrote:
> > >
> > > On Wed, Oct 24, 2018 at 3:37 AM Takashi Iwai <tiwai@suse.de> wrote:
> > > >
> > > > 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.
> > >
> > > I'd really like to see a Sign-off from someone at Creative.  It's not
> > > that I don't trust your word that they agreed to it, but we have
> > > nothing to go back and verify they actually agreed to allow this to be
> > > redistributable, etc.
> > >
> > > josh
> > >
> > > > > ----------------------------------------------------------------
> > > > > 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-11-09 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 17:49 Connor McAdams
2018-10-24  7:37 ` Takashi Iwai
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 [this message]
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=CAM8Agx2KYOZK97J7yiM9JvNF1bxiAKNtA_YDegtLMVAYiWKEXQ@mail.gmail.com \
    --to=conmanx360@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --subject='Re: [GIT PULL] Additional firmware files for CA0132 HD-audio codec' \
    /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

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).