Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: darren.hart@intel.com, Darren Hart <dvhart@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel: use oldnoconfig instead of yes '' | make oldconfig
Date: Tue, 7 Jan 2014 16:54:32 +0100	[thread overview]
Message-ID: <20140107155432.GS3709@jama> (raw)
In-Reply-To: <52CC1B45.9010808@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]

On Tue, Jan 07, 2014 at 04:20:37PM +0100, Alexandre Belloni wrote:
> On 07/01/2014 15:35, Martin Jansa wrote:
> > On Tue, Jan 07, 2014 at 03:18:37PM +0100, Alexandre Belloni wrote:
> >> When using a defconfig, using yes '' | make oldconfig may not result in
> >> the correct configuration being set. For example:
> > 
> >>  $ grep USB_ETH .config
> >>  CONFIG_USB_ETH=y
> >>  CONFIG_USB_ETH_RNDIS=y
> >>  CONFIG_USB_ETH_EEM=y
> >>  $ make savedefconfig
> >>  scripts/kconfig/conf --savedefconfig=defconfig Kconfig
> >>  $ cp defconfig .config
> >>  ‘defconfig’ -> ‘.config’
> >>  $ yes '' | make oldconfig
> >>  [...]
> >>  #
> >>  # configuration written to .config
> >>  #
> >>  $ grep USB_ETH .config
> >>  CONFIG_USB_ETH=m
> >>  CONFIG_USB_ETH_RNDIS=y
> >>  CONFIG_USB_ETH_EEM=y
> >>
> >> Using make olddefconfig solves that but we'll use oldnoconfig for
> >> backward compatibility with older kernels.
> > 
> > Looks good, I have few kernel recipes where I had to fixup resulting
> > .config after "make savedefconfig", "yes '' | make oldconfig" combo
> > exactly because of some =y changing to -m.
> > 
> > 1) Do you know since when oldnoconfig is supported?
> > 
> > IIRC oldest kernel I've in BSPs is 2.6.24. 
> 
> oldnoconfig seems to be present since 2.6.36. olddefconfig is an alias
> that appeared with fb16d8912db5268f29706010ecafff74b971c58d which is
> present since v3.7.
> 
> Then hat about using:
> 
> oe_runmake oldnoconfig || yes '' | oe_runmake oldconfig

Looks safer (assuming that oldnoconfig will return error only in cases
where oldnoconfig target doesn't exist in Makefile, otherwise fall-back
to yes '' could be a bit confusing).

In worst case you can add KERNEL_VERSION check or show bb.warn when
oldnoconfig isn't supported.

> > 2) Could you send similar patch for
> > meta-openembedded/meta-oe/recipes-kernel/linux/linux.inc
> > ?
> > 
> 
> Sure, will do once we agreed on this patch

Thanks

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-01-07 15:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 14:18 [PATCH] kernel: use oldnoconfig instead of yes '' | make oldconfig Alexandre Belloni
2014-01-07 14:35 ` Martin Jansa
2014-01-07 15:20   ` Alexandre Belloni
2014-01-07 15:54     ` Martin Jansa [this message]
2014-01-07 18:11       ` Hart, Darren
2014-01-07 20:32         ` Alexandre Belloni
2014-01-07 21:32           ` Hart, Darren
2014-01-07 15:32 ` Bruce Ashfield
2014-01-07 20:27   ` Alexandre Belloni
2014-01-07 20:39     ` Bruce Ashfield
2014-01-07 20:52       ` Alexandre Belloni
2014-01-07 21:14         ` Bruce Ashfield
2014-01-29 13:10       ` Alexandre Belloni
2014-01-29 15:03         ` Bruce Ashfield
2014-02-06 13:48         ` Bruce Ashfield
2014-02-06 21:48         ` Bruce Ashfield
2014-02-07 14:02           ` Alexandre Belloni
2014-02-07 15:11             ` Bruce Ashfield
2014-02-07 15:43               ` Alexandre Belloni
2014-02-07 16:10                 ` Bruce Ashfield

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=20140107155432.GS3709@jama \
    --to=martin.jansa@gmail.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=darren.hart@intel.com \
    --cc=dvhart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox