From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jesse Zhang <sen.zhang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] two patches for alsa-lib
Date: Mon, 17 Jun 2013 13:35:36 +0100 [thread overview]
Message-ID: <2019586.mcCT5j76os@helios> (raw)
In-Reply-To: <cover.1371472283.git.sen.zhang@windriver.com>
Hi Jesse,
On Monday 17 June 2013 20:33:24 Jesse Zhang wrote:
> The following changes since commit c18249353697f8b3741ae2024308d195671d3598:
>
> rt-tests: fix error check in hackbench (2013-06-17 13:53:42 +0800)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib szhang/alsa
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=szhang/alsa
>
> Jesse Zhang (2):
> alsa-lib: Change function type to "static __inline__"
> alsa-lib: check if wordexp is supported in libc
>
> .../Check-if-wordexp-function-is-supported.patch | 48 +++++++++++++++++
> .../fix-O0-Optimize-unable-inline-function.patch | 61
> ++++++++++++++++++++++ meta/recipes-multimedia/alsa/alsa-lib_1.0.26.bb |
> 2 +
> 3 files changed, 111 insertions(+)
> create mode 100644
> meta/recipes-multimedia/alsa/alsa-lib/Check-if-wordexp-function-is-supporte
> d.patch create mode 100644
> meta/recipes-multimedia/alsa/alsa-lib/fix-O0-Optimize-unable-inline-functio
> n.patch
Could you please add Upstream-Status to the inner patches?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-17 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 12:33 [PATCH 0/2] two patches for alsa-lib Jesse Zhang
2013-06-17 12:33 ` [PATCH 1/2] alsa-lib: Change function type to "static __inline__" Jesse Zhang
2013-06-17 12:33 ` [PATCH 2/2] alsa-lib: check if wordexp is supported in libc Jesse Zhang
2013-06-17 12:35 ` Paul Eggleton [this message]
2013-06-17 12:42 ` [PATCH 0/2] two patches for alsa-lib Jesse Zhang
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=2019586.mcCT5j76os@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sen.zhang@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.