From: Randy Dunlap <rdunlap@infradead.org>
To: Felipe Balbi <balbif@gmail.com>, yann.morin.1998@free.fr
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
balbi@kernel.org, Felipe Balbi <felipe.balbi@linux.intel.com>
Subject: Re: [PATCH] scripts: kconfig: implement a sort method
Date: Thu, 21 Apr 2016 16:12:56 -0700 [thread overview]
Message-ID: <57195E78.9080805@infradead.org> (raw)
In-Reply-To: <1461269279-11525-1-git-send-email-felipe.balbi@linux.intel.com>
On 04/21/16 13:07, Felipe Balbi wrote:
> With a growing amount of Kernel configuration, it's
> getting ever more difficult to find anything on
> menuconfig. Because of that, implement mergesort for
> kconfig to make it a little easier for anybody
> building kernels.
Hi,
Please explain the problem and the solution better. I don't
get it.
Thanks.
> Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
> ---
>
> let me know if you folks prefer to turn this into
> default behavior and drop the extra Sort button, I
> didn't wanna be too disruptive by default and, at
> least for now, kept Kconfig as it is and require
> user to either press '.' or move cursor to the Sort
> button and hit ENTER.
>
> Anyway, give it a go and let me know if anybody sees
> any issues which I might have missed.
>
> scripts/kconfig/lxdialog/menubox.c | 18 +++++----
> scripts/kconfig/mconf.c | 83 +++++++++++++++++++++++++++++++++++---
> 2 files changed, 89 insertions(+), 12 deletions(-)
--
~Randy
next prev parent reply other threads:[~2016-04-21 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 20:07 [PATCH] scripts: kconfig: implement a sort method Felipe Balbi
2016-04-21 23:12 ` Randy Dunlap [this message]
2016-04-22 7:45 ` Felipe Balbi
2016-04-22 17:03 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2017-04-11 11:12 Felipe Balbi
2017-04-11 18:53 ` Randy Dunlap
2017-04-12 7:49 ` Felipe Balbi
2017-04-12 16:06 ` Yann E. MORIN
2017-04-12 18:19 ` Randy Dunlap
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=57195E78.9080805@infradead.org \
--to=rdunlap@infradead.org \
--cc=balbi@kernel.org \
--cc=balbif@gmail.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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