From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 59b08f: Sync kconfig files with upstream 4.15
Date: Mon, 05 Feb 2018 07:26:00 -0000 [thread overview]
Message-ID: <5a780725babb8_233a2aab7291bc14129421@hookshot-fe-d252ca1.cp1-iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 59b08f8d06700770cf1105269acb2ec2460e2a34
https://github.com/crosstool-ng/crosstool-ng/commit/59b08f8d06700770cf1105269acb2ec2460e2a34
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2018-01-31 (Wed, 31 Jan 2018)
Changed paths:
M kconfig/.gitignore
M kconfig/Makefile.in
M kconfig/check.sh
M kconfig/conf.c
M kconfig/expr.c
M kconfig/expr.h
A kconfig/kconf_id.c
M kconfig/list.h
M kconfig/lkc.h
M kconfig/lkc_proto.h
M kconfig/lxdialog/check-lxdialog.sh
M kconfig/menu.c
M kconfig/nconf.c
M kconfig/nconf.gui.c
M kconfig/symbol.c
R kconfig/zconf.gperf
M kconfig/zconf.y
Log Message:
-----------
Sync kconfig files with upstream 4.15
Last updated with 4.9-rc7.
This commit introduces the following upstream changes:
9059a3493efe kconfig: fix relational operators for bool and tristate symbols
88127dae6ed9 kconfig/symbol.c: use correct pointer type argument for sizeof
b24413180f56 License cleanup: add SPDX GPL-2.0 license identifier to files with no license
bb3290d91695 Remove gperf usage from toolchain
ad8181060788 kconfig: fix sparse warnings in nconfig
ff85a1a80e00 kconfig: Check for libncurses before menuconfig
9be3213b14d4 gconfig: remove misleading parentheses around a condition
83c3a1bad224 xconfig: fix missing suboption and help panels on first run
e039303ff71a xconfig: fix 'Show Debug' functionality
79e51b5c2dee kconfig/nconf: Fix hang when editing symbol with a long prompt
0eb47346968f Scripts: kconfig: nconf: fix _GNU_SOURCE redefined warning
237e3ad0f195 Kconfig: Introduce the "imply" keyword
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: 04d910b8267856b345db93a5395212c4f7cd9199
https://github.com/crosstool-ng/crosstool-ng/commit/04d910b8267856b345db93a5395212c4f7cd9199
Author: Alexey Neyman <stilor@att.net>
Date: 2018-02-04 (Sun, 04 Feb 2018)
Changed paths:
M kconfig/.gitignore
M kconfig/Makefile.in
M kconfig/check.sh
M kconfig/conf.c
M kconfig/expr.c
M kconfig/expr.h
A kconfig/kconf_id.c
M kconfig/list.h
M kconfig/lkc.h
M kconfig/lkc_proto.h
M kconfig/lxdialog/check-lxdialog.sh
M kconfig/menu.c
M kconfig/nconf.c
M kconfig/nconf.gui.c
M kconfig/symbol.c
R kconfig/zconf.gperf
M kconfig/zconf.y
Log Message:
-----------
Merge pull request #907 from bhundven/update_kconfig_4_15
Sync kconfig files with upstream 4.15
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/dfcb5fe3c14d...04d910b82678
next reply other threads:[~2018-02-05 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 7:26 Alexey Neyman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-01 0:42 Bryan Hundven
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=5a780725babb8_233a2aab7291bc14129421@hookshot-fe-d252ca1.cp1-iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).