public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Du, Changbin" <changbin.du@intel.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: Michal Marek <mmarek@suse.com>, Jonathan Corbet <corbet@lwn.net>,
	yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org,
	linux-doc <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Documentation/kconfig: add search jump feature description
Date: Tue, 7 Feb 2017 11:06:05 +0800	[thread overview]
Message-ID: <20170207030605.GA32621@intel.com> (raw)
In-Reply-To: <CA+r1ZhgO-jkcsRxOvhtPa4Pd1Mz1GXnH4cpnWdreBMtXeAkoSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

On Mon, Feb 06, 2017 at 07:42:11AM -0700, Jim Davis wrote:
> On Mon, Feb 6, 2017 at 12:46 AM,  <changbin.du@intel.com> wrote:
> > From: Changbin Du <changbin.du@intel.com>
> >
> > Kernel menuconfig support direct jumping function from the search
> > result. This is a very convenient feature but not documented. So
> > add a short description to the kconfig documentation to let more
> > developer know it.
> >
> > Signed-off-by: Changbin Du <changbin.du@intel.com>
> > ---
> >  Documentation/kbuild/kconfig.txt | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/kbuild/kconfig.txt b/Documentation/kbuild/kconfig.txt
> > index bbc99c0..9916318 100644
> > --- a/Documentation/kbuild/kconfig.txt
> > +++ b/Documentation/kbuild/kconfig.txt
> > @@ -178,6 +178,10 @@ Searching in menuconfig:
> >         first (and in alphabetical order), then come all other symbols,
> >         sorted in alphabetical order.
> >
> > +       In the search result textbox, each symbol has a jump number on
> > +       left side if the symbol is jumpable. You can type the nubmer
> 
> number  ("jumpable" reads a bit oddly, but it is understandable.)
> 
How about 'if the symbol is visible'?

> > +       to jump to target menu to configurate that symbol.
> 
> configure?
>
Thanks, I will correct them.

> -- 
> Jim

-- 
Thanks,
Changbin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2017-02-07  3:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  7:46 [PATCH 0/2] kconfig/mconf: propagate jumping function in search result view changbin.du
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 [this message]
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=20170207030605.GA32621@intel.com \
    --to=changbin.du@intel.com \
    --cc=corbet@lwn.net \
    --cc=jim.epost@gmail.com \
    --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