alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Curtis Malainey <cujomalainey@google.com>,
	ALSA development <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.com>
Cc: Dylan Reid <dgreid@google.com>,
	Jimmy Cheng-Yi Chiang <cychiang@google.com>
Subject: Re: [alsa-devel] alsa-ucm-conf via portage on arm
Date: Fri, 14 Feb 2020 19:38:57 +0100	[thread overview]
Message-ID: <23daf96d-f854-f01f-bc4e-2afc47299c0a@perex.cz> (raw)
In-Reply-To: <CAOReqxhbvG03QvqkbjnGB8w5cM4WOK4qeZ+bh0apNna7i3ZimA@mail.gmail.com>

Dne 14. 02. 20 v 19:23 Curtis Malainey napsal(a):
> Hello Takashi and Jaroslav,
> 
> There appears to be a upstream package issue for alsa-ucm-conf in that
> portage seems to have it restricted to x86 and amd64 platforms. Given
> the nature of the ucms I figure this is an error and was hoping you
> know who to speak to in order to resolve this. If this isn't an error
> what can I do to help get the repo to state in which it is supported
> on arm/arm64?
> 
> See https://gitweb.gentoo.org/repo/gentoo.git/commit/media-libs/alsa-ucm-conf/alsa-ucm-conf-1.2.1.2.ebuild?id=dd3e0570e2465639431709bce0410b787d312bbe
> 
> Curtis

It's Gentoo specific and you see signed-off-by in this commit.

Did you contact this person (Lars Wendler) from Gentoo?

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2020-02-14 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 18:23 [alsa-devel] alsa-ucm-conf via portage on arm Curtis Malainey
2020-02-14 18:38 ` Jaroslav Kysela [this message]
2020-02-14 18:45   ` Curtis Malainey

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=23daf96d-f854-f01f-bc4e-2afc47299c0a@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=cujomalainey@google.com \
    --cc=cychiang@google.com \
    --cc=dgreid@google.com \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).