From: Rongqing Li <rongqing.li@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] busybox: add the dropped patches back
Date: Thu, 6 Nov 2014 13:34:07 +0800 [thread overview]
Message-ID: <545B084F.9010907@windriver.com> (raw)
In-Reply-To: <1415248440-28251-1-git-send-email-rongqing.li@windriver.com>
please drop it, thanks
-Roy
On Thursday, November 06, 2014 12:34 PM, rongqing.li@windriver.com wrote:
> From: "Roy.Li" <rongqing.li@windriver.com>
>
> busybox-cross-menuconfig.patch and busybox-install-ping6-to-usr-bin.patch
> were dropped when uprev, add them back.
>
> no busybox-cross-menuconfig.patch, "bitbake -c menuconfig busybox" did not
> work.
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
> .../{busybox-1.21.1 => busybox-1.22.1}/busybox-cross-menuconfig.patch | 0
> .../busybox-install-ping6-to-usr-bin.patch | 0
> meta/recipes-core/busybox/busybox_1.22.1.bb | 2 ++
> 3 files changed, 2 insertions(+)
> rename meta/recipes-core/busybox/{busybox-1.21.1 => busybox-1.22.1}/busybox-cross-menuconfig.patch (100%)
> rename meta/recipes-core/busybox/{busybox-1.21.1 => busybox-1.22.1}/busybox-install-ping6-to-usr-bin.patch (100%)
>
> diff --git a/meta/recipes-core/busybox/busybox-1.21.1/busybox-cross-menuconfig.patch b/meta/recipes-core/busybox/busybox-1.22.1/busybox-cross-menuconfig.patch
> similarity index 100%
> rename from meta/recipes-core/busybox/busybox-1.21.1/busybox-cross-menuconfig.patch
> rename to meta/recipes-core/busybox/busybox-1.22.1/busybox-cross-menuconfig.patch
> diff --git a/meta/recipes-core/busybox/busybox-1.21.1/busybox-install-ping6-to-usr-bin.patch b/meta/recipes-core/busybox/busybox-1.22.1/busybox-install-ping6-to-usr-bin.patch
> similarity index 100%
> rename from meta/recipes-core/busybox/busybox-1.21.1/busybox-install-ping6-to-usr-bin.patch
> rename to meta/recipes-core/busybox/busybox-1.22.1/busybox-install-ping6-to-usr-bin.patch
> diff --git a/meta/recipes-core/busybox/busybox_1.22.1.bb b/meta/recipes-core/busybox/busybox_1.22.1.bb
> index 82f7f68..2a4e647 100644
> --- a/meta/recipes-core/busybox/busybox_1.22.1.bb
> +++ b/meta/recipes-core/busybox/busybox_1.22.1.bb
> @@ -6,6 +6,8 @@ SRC_URI = "http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \
> file://get_header_tar.patch \
> file://busybox-appletlib-dependency.patch \
> file://busybox-udhcpc-no_deconfig.patch \
> + file://busybox-cross-menuconfig.patch \
> + file://busybox-install-ping6-to-usr-bin.patch \
> file://find-touchscreen.sh \
> file://busybox-cron \
> file://busybox-httpd \
>
--
Best Reagrds,
Roy | RongQing Li
prev parent reply other threads:[~2014-11-06 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 4:34 [PATCH 1/1] busybox: add the dropped patches back rongqing.li
2014-11-06 5:34 ` Rongqing Li [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=545B084F.9010907@windriver.com \
--to=rongqing.li@windriver.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