All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1 v2][PULL] procps: fix hardcoded libdir
Date: Wed, 24 Aug 2011 16:33:03 -0700	[thread overview]
Message-ID: <4E558A2F.20707@linux.intel.com> (raw)
In-Reply-To: <cover.1314109766.git.dongxiao.xu@intel.com>

On 08/23/2011 07:32 AM, Dongxiao Xu wrote:
> Hi Richard and Saul,
>
> This is the second pull request that fixes the hardcoded libdir in procps to support multilib.
> Please help to review and pull.
>
> Thanks,
> Dongxiao
>
>
> The following changes since commit 9134800548a03bfe3a7e351a15f2129bcb3cc680:
>
>    xcb/libpthreads: Add BBCLASSEXTEND to resolve missing providers in world builds (2011-08-19 16:27:29 -0700)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib dxu4/multilib
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/multilib
>
> Dongxiao Xu (1):
>    procps: Fix lib path to support multilib
>
>   .../procps/procps-3.2.8/install.patch              |   30 +++++++++++++------
>   meta/recipes-extended/procps/procps_3.2.8.bb       |    8 ++--
>   2 files changed, 24 insertions(+), 14 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2011-08-24 23:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 14:32 [PATCH 0/1 v2][PULL] procps: fix hardcoded libdir Dongxiao Xu
2011-08-23 14:32 ` [PATCH 1/1] procps: Fix lib path to support multilib Dongxiao Xu
2011-08-24 23:33 ` Saul Wold [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=4E558A2F.20707@linux.intel.com \
    --to=sgw@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 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.