From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.cz>,
Jean Delvare <jdelvare@suse.de>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: [pull request] Pull request for branch yem-kconfig-rc-fixes
Date: Tue, 16 Jul 2013 22:39:56 +0200 [thread overview]
Message-ID: <cover.1374006854.git.yann.morin.1998@free.fr> (raw)
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Hello Michal,
Please pull these post-rc1 kconfig cleanups, all after
review and comments by Jean:
- simplify and cleanup the symbol-search code
- better documentation about the symbols ordering in search results
- eye-candy in the title of the search-box in [mn]conf
Regards,
Yann E. MORIN.
The following changes since commit b57caaaed2bd127fe656e6c145970ed6a05c0125:
kconfig: allow "hex" and "range" to support longs (2013-06-29 15:30:17 +0200)
are available in the git repository at:
git://gitorious.org/linux-kconfig/linux-kconfig.git yem-kconfig-rc-fixes
for you to fetch changes up to 508382a0428f2b2f49da0e0e89c921f07c9306aa:
kconfig: simplify symbol-search code (2013-07-16 20:39:42 +0200)
----------------------------------------------------------------
Yann E. MORIN (6):
Documentation/kconfig: more concise and straightforward search explanation
kconfig: avoid multiple calls to strlen
kconfig/[mn]conf: shorten title in search-box
kconfig: minor style fixes in symbol-search code
kconfig: don't allocate n+1 elements in temporary array
kconfig: simplify symbol-search code
Documentation/kbuild/kconfig.txt | 8 +++----
scripts/kconfig/mconf.c | 4 ++--
scripts/kconfig/nconf.c | 4 ++--
scripts/kconfig/symbol.c | 49 ++++++++++++++++------------------------
4 files changed, 27 insertions(+), 38 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2013-07-16 20:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 20:39 Yann E. MORIN [this message]
2013-07-16 20:39 ` [PATCH 1/6] Documentation/kconfig: more concise and straightforward search explanation Yann E. MORIN
2013-07-16 20:39 ` [PATCH 2/6] kconfig: avoid multiple calls to strlen Yann E. MORIN
2013-07-16 20:39 ` [PATCH 3/6] kconfig/[mn]conf: shorten title in search-box Yann E. MORIN
2013-07-17 9:55 ` Jean Delvare
2013-07-16 20:40 ` [PATCH 4/6] kconfig: minor style fixes in symbol-search code Yann E. MORIN
2013-07-16 20:40 ` [PATCH 5/6] kconfig: don't allocate n+1 elements in temporary array Yann E. MORIN
2013-07-16 20:40 ` [PATCH 6/6] kconfig: simplify symbol-search code Yann E. MORIN
2013-07-17 9:59 ` [pull request] Pull request for branch yem-kconfig-rc-fixes Jean Delvare
2013-07-23 13:37 ` Michal Marek
2013-07-23 13:54 ` Yann E. MORIN
2013-07-23 14:36 ` Michal Marek
-- strict thread matches above, loose matches on Subject: below --
2013-05-20 15:48 Yann E. MORIN
2013-05-29 21:50 ` Yann E. MORIN
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=cover.1374006854.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=jdelvare@suse.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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 NNTP newsgroup(s).