From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Kconfig: sync with linux kernel v2.6.35-4771-g1787985
Date: Mon, 23 Aug 2010 04:51:23 +0200 [thread overview]
Message-ID: <20100823025123.GP8693@game.jcrosoft.org> (raw)
In-Reply-To: <87wrrikdtd.fsf@macbook.be.48ers.dk>
On 14:54 Sun 22 Aug , Peter Korsgaard wrote:
> >>>>> "Robert" == Robert Schwebel <r.schwebel@pengutronix.de> writes:
>
> [Sorry, old thread - Been away on vacation]
>
> >> Which bring up another question. We have plenty of projects out there
> >> that rely on kconfig.
>
> Robert> ptxdist as well.
>
> And Buildroot and OpenWrt and crosstool-ng, ...
>
> >> What can we do to kconfig to make the integration easier?
> >>
> >> We have discussed that kconfig should be a seperate installable tool
> >> (as rpm, deb whatever). But there is a few quirks needed before we can
> >> do so.
>
> Robert> I don't think that it is necessary. Last time I checked the most
> Robert> complicated thing was to exchange the project name ("Linux kernel") to
> Robert> something else, because there were quite a lot of hand coded numbers
> Robert> representing the string length or length-1. But we are not up to the
> Robert> latest versions - I'll have to re-check.
>
> Yeah. Buildroot has historically done s/CONFIG_/BR2_/ as well, but I'm
> strongly considering going back to CONFIG_.
I agree too
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-08-23 2:51 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 [this message]
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
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=20100823025123.GP8693@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=jacmet@sunsite.dk \
/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