From: changbin.du@intel.com
To: mmarek@suse.com, corbet@lwn.net
Cc: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Changbin Du <changbin.du@intel.com>
Subject: [PATCH 0/2] kconfig/mconf: propagate jumping function in search result view
Date: Mon, 6 Feb 2017 15:46:46 +0800 [thread overview]
Message-ID: <20170206074648.23896-1-changbin.du@intel.com> (raw)
From: Changbin Du <changbin.du@intel.com>
While I am searching something in menuconfig, I hope if I can jump to interested
items directly. I even try to add this feature. When I check the code just found
it has already been there but not documented. So why let more developers know it?
Changbin Du (2):
kconfig/mconf: add jumping tip in title of search result textbox
Documentation/kconfig: add search jump feature description
Documentation/kbuild/kconfig.txt | 4 ++++
scripts/kconfig/mconf.c | 8 ++++----
2 files changed, 8 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-06 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 7:46 changbin.du [this message]
2017-02-06 7:46 ` [PATCH 1/2] kconfig/mconf: add jumping tip in title of search result textbox changbin.du
2017-02-06 12:00 ` Jani Nikula
2017-02-07 3:10 ` Du, Changbin
2017-02-06 7:46 ` [PATCH 2/2] Documentation/kconfig: add search jump feature description changbin.du
2017-02-06 14:42 ` Jim Davis
2017-02-07 3:06 ` Du, Changbin
2017-02-08 3:09 ` [PATCH v2 0/2] kconfig/mconf: propagate jumping function in search result view changbin.du
2017-03-06 10:28 ` Du, Changbin
2017-03-23 5:35 ` Du, Changbin
2017-03-23 10:17 ` Jani Nikula
2017-02-08 3:09 ` [PATCH v2 1/2] kconfig/mconf: add jumping tip in title of search result textbox changbin.du
2017-02-08 8:07 ` Jani Nikula
2017-02-08 3:09 ` [PATCH v2 2/2] Documentation/kconfig: add search jump feature description changbin.du
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=20170206074648.23896-1-changbin.du@intel.com \
--to=changbin.du@intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yann.morin.1998@free.fr \
/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