From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v3 1/1] support/kconfig: Bump to kconfig from Linux 4.17-rc2
Date: Wed, 19 Sep 2018 16:20:49 +0200 [thread overview]
Message-ID: <20180919162049.7067401e@windsurf> (raw)
In-Reply-To: <20180919140756.GA2353@x230>
Hello,
On Wed, 19 Sep 2018 16:07:57 +0200, Petr Vorel wrote:
> Sure :). v2 build all code no matter whether it was actually needed. E.g. 'make
> menuconfig' built gconf (gtk) or qconf (qt). That's a bug you pointed out in
> [1]. I fixed it in v3. It was caused by removing ifeq clauses.
> Here is the diff v2 vs. v3:
Aah, OK. Much clearer explanation, thanks!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-19 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 11:36 [Buildroot] [RFC PATCH v3 1/1] support/kconfig: Bump to kconfig from Linux 4.17-rc2 Petr Vorel
2018-09-19 13:28 ` Thomas Petazzoni
2018-09-19 14:07 ` Petr Vorel
2018-09-19 14:20 ` Thomas Petazzoni [this message]
2018-09-20 21:20 ` Thomas Petazzoni
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=20180919162049.7067401e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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