All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Felipe Balbi <balbif@gmail.com>,
	yann.morin.1998@free.fr
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: kconfig: implement a sort method
Date: Fri, 22 Apr 2016 10:45:11 +0300	[thread overview]
Message-ID: <87shye84u0.fsf@intel.com> (raw)
In-Reply-To: <57195E78.9080805@infradead.org>

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


Hi,

Randy Dunlap <rdunlap@infradead.org> writes:
> 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.

it's unclear to me what you don't understand from description above. Try
to find and enable some random driver on menuconfig. Here's a
suggestion:

"Maxim Semiconductor MAX77843 PMIC Support"

In any case, the idea is the following:

menuconfig has too many options, they are unsorted -> sort them

-- 
balbi

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

  reply	other threads:[~2016-04-22  7:47 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
2016-04-22  7:45   ` Felipe Balbi [this message]
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=87shye84u0.fsf@intel.com \
    --to=balbi@kernel.org \
    --cc=balbif@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.