From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] task-base: add alsa-state to task-base-alsa
Date: Fri, 13 Jan 2012 10:54:38 -0800 [thread overview]
Message-ID: <4F107DEE.4020106@linux.intel.com> (raw)
In-Reply-To: <20120112163127.GG3452@jama.jama.net>
On 12/01/12 08:31, Martin Jansa wrote:
> On Thu, Jan 12, 2012 at 08:23:16AM -0800, Darren Hart wrote:
>>
>>
>> On 01/10/2012 09:39 AM, Joshua Lock wrote:
>>> This enables automatic configuration setting and restoration on systems
>>> with alsa.
>>>
>>> Signed-off-by: Joshua Lock<josh@linux.intel.com>
>>
>> Acked-by: Darren Hart<dvhart@linux.intel.com>
>
> can we use VIRTUAL_RUNTIME for this, please?
>
> for example in SHR we have alsa-state provided by fsoaudiod
That's a fine idea. VIRTUAL-RUNTIME_alsa-state?
I'm testing a patch for it now.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-13 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 17:39 [PATCH 0/3] Add alsa-state from OE Classic v2 Joshua Lock
2012-01-10 17:39 ` [PATCH 1/3] alsa-state: add alsa-state from oe classic Joshua Lock
2012-01-10 19:30 ` Otavio Salvador
2012-01-10 19:44 ` Joshua Lock
2012-01-12 16:22 ` Darren Hart
2012-01-10 17:39 ` [PATCH 2/3] alsa-state: move state files to localstatedir Joshua Lock
2012-01-12 16:23 ` Darren Hart
2012-01-10 17:39 ` [PATCH 3/3] task-base: add alsa-state to task-base-alsa Joshua Lock
2012-01-12 16:23 ` Darren Hart
2012-01-12 16:31 ` Martin Jansa
2012-01-13 18:54 ` Joshua Lock [this message]
2012-01-13 18:58 ` Martin Jansa
2012-01-10 19:34 ` [PATCH 0/3] Add alsa-state from OE Classic v2 Otavio Salvador
2012-01-10 19:45 ` Joshua Lock
2012-01-10 19:48 ` Otavio Salvador
2012-01-24 23:37 ` Joshua Lock
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=4F107DEE.4020106@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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