From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: fuweix.tang@intel.com
Cc: tiwai@suse.de, mengdong.lin@intel.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 0/3] ucm-conf: Add intel UCM conf files to alsa-ucm-conf repo
Date: Wed, 12 Apr 2017 15:50:57 +0100 [thread overview]
Message-ID: <1492008657.3482.184.camel@loki> (raw)
In-Reply-To: <cover.1490064444.git.fuweix.tang@intel.com>
On Wed, 2017-04-12 at 16:54 +0800, fuweix.tang@intel.com wrote:
> From: Fuwei Tang <fuweix.tang@intel.com>
>
> Add the intel UCM configs to a dedicated UCM conf repo and release them using
> the BSD license.
We are still missing the LICENSE/COPYING file. We need to add it the top
directory level so it's clear to users.
> The other non intel UCM files can be moved over when there is agreement with the
> file authors, but in the mean time they will stay in alsa-lib.
> The configs are moved from alsa-lib repo. The original authorship and commit
> message of all config files will be reserved.
>
Takashi, how do you want to manage the move ? We could add the files to
the new repo first and then only delete them in alsa-lib after the next
alsa-lib release ? This would give time for distros to pick up the new
conf package. I'm easy on whatever works best here.
Thanks
Liam
> Fuwei Tang (1):
> ucm-conf: Set up for installation
>
> Vinod Koul (2):
> ucm-conf: broxton: add broxton-rt298 conf files
> ucm-conf: skylake: add skylake-rt286 conf files
>
> .gitignore | 12 ++++
> ChangeLog | 1 +
> INSTALL | 1 +
> Makefile.am | 1 +
> broxton-rt298/Hdmi1 | 22 +++++++
> broxton-rt298/Hdmi2 | 14 +++++
> broxton-rt298/HiFi | 129 +++++++++++++++++++++++++++++++++++++++
> broxton-rt298/Makefile.am | 4 ++
> broxton-rt298/broxton-rt298.conf | 58 ++++++++++++++++++
> configure.ac | 24 ++++++++
> gitcompile | 5 ++
> skylake-rt286/Hdmi1 | 20 ++++++
> skylake-rt286/Hdmi2 | 20 ++++++
> skylake-rt286/HiFi | 129 +++++++++++++++++++++++++++++++++++++++
> skylake-rt286/Makefile.am | 4 ++
> skylake-rt286/skylake-rt286.conf | 60 ++++++++++++++++++
> 16 files changed, 504 insertions(+)
> create mode 100644 .gitignore
> create mode 100644 ChangeLog
> create mode 120000 INSTALL
> create mode 100644 Makefile.am
> create mode 100644 broxton-rt298/Hdmi1
> create mode 100644 broxton-rt298/Hdmi2
> create mode 100644 broxton-rt298/HiFi
> create mode 100644 broxton-rt298/Makefile.am
> create mode 100644 broxton-rt298/broxton-rt298.conf
> create mode 100644 configure.ac
> create mode 100755 gitcompile
> create mode 100644 skylake-rt286/Hdmi1
> create mode 100644 skylake-rt286/Hdmi2
> create mode 100644 skylake-rt286/HiFi
> create mode 100644 skylake-rt286/Makefile.am
> create mode 100644 skylake-rt286/skylake-rt286.conf
>
next prev parent reply other threads:[~2017-04-12 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 3:15 [PATCH v2 0/3] ucm-conf: Add intel UCM conf files to alsa-ucm-conf repo fuweix.tang
2017-03-21 3:15 ` [PATCH v2 1/3] ucm-conf: Set up for installation fuweix.tang
2017-03-21 3:15 ` [PATCH v2 2/3] ucm-conf: broxton: add broxton-rt298 conf files fuweix.tang
2017-03-21 3:15 ` [PATCH v2 3/3] ucm-conf: skylake: add skylake-rt286 " fuweix.tang
2017-04-12 14:50 ` Liam Girdwood [this message]
2017-04-12 14:57 ` [PATCH v2 0/3] ucm-conf: Add intel UCM conf files to alsa-ucm-conf repo Takashi Iwai
2017-04-12 15:10 ` Jaroslav Kysela
2017-04-12 15:26 ` Liam Girdwood
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=1492008657.3482.184.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=fuweix.tang@intel.com \
--cc=mengdong.lin@intel.com \
--cc=tiwai@suse.de \
/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).