From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] alsa-lib: use PKGSUFFIX for every package to resolve multiple runtime providers from target and nativesdk
Date: Tue, 15 Nov 2011 12:20:38 +0000 [thread overview]
Message-ID: <1321359638.26881.174.camel@ted> (raw)
In-Reply-To: <1321276032-5110-1-git-send-email-Martin.Jansa@gmail.com>
On Mon, 2011-11-14 at 14:07 +0100, Martin Jansa wrote:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/recipes-multimedia/alsa/alsa-lib_1.0.24.1.bb | 19 +++++++++++--------
> 1 files changed, 11 insertions(+), 8 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-11-15 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5050804@linux.intel.com>
2011-11-12 7:35 ` [PATCH] default-providers: add alsa to resolve multiple runtime providers Martin Jansa
2011-11-12 8:03 ` Richard Purdie
2011-11-12 8:06 ` Koen Kooi
2011-11-12 18:19 ` Richard Purdie
2011-11-14 13:07 ` [PATCH] alsa-lib: use PKGSUFFIX for every package to resolve multiple runtime providers from target and nativesdk Martin Jansa
2011-11-15 12:20 ` Richard Purdie [this message]
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=1321359638.26881.174.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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