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: Thu, 20 Sep 2018 23:20:14 +0200 [thread overview]
Message-ID: <20180920232014.1c19988b@windsurf> (raw)
In-Reply-To: <20180919113615.27036-1-petr.vorel@gmail.com>
Hello,
On Wed, 19 Sep 2018 13:36:15 +0200, Petr Vorel wrote:
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Changes v2->v3:
> * Fix issues with building more that we need (menuconfig require
> unfortunately "make menuconfig" fails, because
> it wants ? reported by Thomas in [1]).
You forgot to "git add" the kconf_id.c file, so it was missing from the
patch. I've re-added it from the 4.17-rc2 Linux kernel source code, and
that fixed the problem, I was able to test
menuconfig/nconfig/xconfig/savedefconfig.
Applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-20 21: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
2018-09-20 21:20 ` Thomas Petazzoni [this message]
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=20180920232014.1c19988b@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 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.