From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : linux.inc: add back 'yes '' | oe_runmake oldconfig' that got dropped
Date: Fri, 06 Mar 2009 12:46:09 +0100 [thread overview]
Message-ID: <49B10D01.2080801@gmx.de> (raw)
In-Reply-To: <20090306064607.C5FCC1880D9@amethyst.openembedded.net>
GIT User account schrieb:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: cdd27f17b730c0f5ba537fdee6a9086549f67410
> URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=cdd27f17b730c0f5ba537fdee6a9086549f67410
>
> Author: Koen Kooi <koen@openembedded.org>
> Date: Fri Mar 6 07:44:00 2009 +0100
>
> linux.inc: add back 'yes '' | oe_runmake oldconfig' that got dropped
>
> ---
>
> packages/linux/linux.inc | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/packages/linux/linux.inc b/packages/linux/linux.inc
> index f3d3bf8..984efac 100644
> --- a/packages/linux/linux.inc
> +++ b/packages/linux/linux.inc
> @@ -124,6 +124,7 @@ do_configure_prepend() {
> echo "CONFIG_ROOT_NFS=y" >> ${S}/.config
> echo "CONFIG_CMDLINE=\"${CMDLINE_NFSROOT_USB}\"" >> ${S}/.config
> fi
> + yes '' | oe_runmake oldconfig
> }
>
> do_configure_append_avr32() {
>
>
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
>
I dropped it accidentally, but the same line is already in do_configure
from kernel.bbclass. As we only prepend this task there is no reason to
duplicate it, isn't it?
parent reply other threads:[~2009-03-06 11:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090306064607.C5FCC1880D9@amethyst.openembedded.net>]
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=49B10D01.2080801@gmx.de \
--to=thommycheck@gmx.de \
--cc=openembedded-devel@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.