All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>,
	<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH V2 0/4] Packages upgrade: groff and directfb
Date: Fri, 9 Jan 2015 19:50:38 +0800	[thread overview]
Message-ID: <54AFC08E.2040401@windriver.com> (raw)
In-Reply-To: <cover.1419823473.git.hongxu.jia@windriver.com>

On 12/29/2014 01:47 PM, Hongxu Jia wrote:
> Changed in V2:

Ping

//Hongxu

> - Follow Saul's suggestions, investigate groff's README, double
>    check its DEPENDS;
>
> - Follow Richard's suggestions, correctly set the path to perl
>    in the recipe.
>
> - Fix qt4-embedded build failure which caused by the upgraded
>    directfb. (thanks Richard and Otavio for pointing it out)
>
> //Hongxu
>
>
> The following changes since commit e3a623bfe39fda16420d2042647af75877bb6f70:
>
>    runqemu-internal: increase memory for qemuarm64 (2014-12-25 08:27:13 +0000)
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib hongxu/upgrade-packages
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/upgrade-packages
>
> Hongxu Jia (4):
>    groff: upgrade 1.22.3
>    groff: fix native perl path
>    directfb: upgrade to 1.7.6
>    qt4-embedded: support c++0x stand for directfb
>
>   ...off-1.22.2-correct-man.local-install-path.patch |  32 --
>   .../groff-correct-man.local-install-path.patch     |  45 +++
>   .../groff/{groff_1.22.2.bb => groff_1.22.3.bb}     |  23 +-
>   .../directfb/directfb/fixsepbuild.patch            |  19 --
>   .../rename-no-instrument-function-macro.patch      | 345 ---------------------
>   .../{directfb_1.7.4.bb => directfb_1.7.6.bb}       |   8 +-
>   ...figure-support-c-0x-standard-for-directfd.patch |  40 +++
>   meta/recipes-qt/qt4/qt4-embedded.inc               |   4 +-
>   8 files changed, 99 insertions(+), 417 deletions(-)
>   delete mode 100644 meta/recipes-extended/groff/groff-1.22.2/groff-1.22.2-correct-man.local-install-path.patch
>   create mode 100644 meta/recipes-extended/groff/groff-1.22.3/groff-correct-man.local-install-path.patch
>   rename meta/recipes-extended/groff/{groff_1.22.2.bb => groff_1.22.3.bb} (72%)
>   delete mode 100644 meta/recipes-graphics/directfb/directfb/fixsepbuild.patch
>   delete mode 100644 meta/recipes-graphics/directfb/directfb/rename-no-instrument-function-macro.patch
>   rename meta/recipes-graphics/directfb/{directfb_1.7.4.bb => directfb_1.7.6.bb} (58%)
>   create mode 100644 meta/recipes-qt/qt4/qt4-4.8.6/0033-configure-support-c-0x-standard-for-directfd.patch
>



  parent reply	other threads:[~2015-01-09 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  5:47 [PATCH V2 0/4] Packages upgrade: groff and directfb Hongxu Jia
2014-12-29  5:47 ` [PATCH 1/4] groff: upgrade 1.22.3 Hongxu Jia
2014-12-29  5:47 ` [PATCH 2/4] groff: fix native perl path Hongxu Jia
2014-12-29  5:47 ` [PATCH 3/4] directfb: upgrade to 1.7.6 Hongxu Jia
2014-12-29  5:47 ` [PATCH 4/4] qt4-embedded: support c++0x stand for directfb Hongxu Jia
2015-01-09 11:50 ` Hongxu Jia [this message]
2015-01-09 12:42 ` [PATCH V2 0/4] Packages upgrade: groff and directfb Burton, Ross
2015-01-12  2:04   ` Hongxu Jia

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=54AFC08E.2040401@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.