mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Kconfig: sync with linux kernel v2.6.35-4771-g1787985
Date: Sun, 22 Aug 2010 07:07:10 +0200	[thread overview]
Message-ID: <20100822050710.GN8693@game.jcrosoft.org> (raw)
In-Reply-To: <20100821113550.GA25293@merkur.ravnborg.org>

On 13:35 Sat 21 Aug     , Sam Ravnborg wrote:
> On Sat, Aug 21, 2010 at 12:27:34PM +0200, Sascha Hauer wrote:
> > On Wed, Aug 18, 2010 at 05:15:36PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > On 06:17 Sun 08 Aug     , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > this will add also the support of the new ncurse interface nconfig
> > > > 
> > > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > > is it ok to apply it?
> > 
> > Generally ok, yes. I just thought we should wait a little for a later
> > version, or have I misunderstood Sam?
> 
> Current state of kconfig in v2.6.36-rc1 (which is a later version than
> the one Jean-Christophe references) is the following:
> - savedefconfig bugs fixed
> - reading a minimal config (created by savedefconfig) fixed
> 
> The nconfig issues I mentioned regarding search are
> not yet ready.
> And I am not sure if they go in until next merge window.
> 
> Likewise there are patches in the works that will ease
> the integration with external projects.
> The patches does the following:
> - Allows the prefix to be configured (CONFIG_ => BR2_)
> - No more hardcoded "kernel" strings
> - mainmenu in the config file is used as headline
> 
> These patches will go in during next merge window if they
> are finished in due time.
> 
> So all-in-all I would recommend to use kconfig from
> v2.6.36-rc1 (rather than some random commit) and
> then upgrade again around v2.6.37-rc1 time.
ok I upgrade the patch

and it will be good to update it regulary I will follow it
is there a ML for Kconfig?

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-08-22  5:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08  4:17 Jean-Christophe PLAGNIOL-VILLARD
2010-08-08  6:48 ` Sam Ravnborg
2010-08-08  9:06   ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-08 12:07     ` Sam Ravnborg
2010-08-08 12:20       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-13 19:26     ` Sam Ravnborg
2010-08-14  4:35       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-14  6:51         ` Sam Ravnborg
2010-08-09  6:49   ` Robert Schwebel
2010-08-22 12:54     ` Peter Korsgaard
2010-08-23  2:51       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-18 15:15 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-21 10:27   ` Sascha Hauer
2010-08-21 11:35     ` Sam Ravnborg
2010-08-22  5:07       ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-08-22  5:55         ` Sam Ravnborg
2010-08-22 13:48       ` Peter Korsgaard
2010-08-24 17:59       ` Uwe Kleine-König
2010-08-22  5:17 ` [PATCH v2] Kconfig: sync with linux kernel v2.6.36-rc1-168-ge36c886 Jean-Christophe PLAGNIOL-VILLARD

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=20100822050710.GN8693@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=sam@ravnborg.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