From: Jiri Pirko <jiri@resnulli.us>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jiri Pirko <jiri@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lib: Introduce priority array area manager
Date: Thu, 23 Feb 2017 09:32:31 +0100 [thread overview]
Message-ID: <20170223083231.GA2699@nanopsycho> (raw)
In-Reply-To: <CAMuHMdXR5QZrN1NMkZq_jSo0cRMqMJ6m5q-8C3pr1_NWKUZcqg@mail.gmail.com>
Thu, Feb 23, 2017 at 08:56:26AM CET, geert@linux-m68k.org wrote:
>Hi Jiri,
>
>On Wed, Feb 22, 2017 at 8:02 PM, Linux Kernel Mailing List
><linux-kernel@vger.kernel.org> wrote:
>> Web: https://git.kernel.org/torvalds/c/44091d29f2075972aede47ef17e1e70db3d51190
>> Commit: 44091d29f2075972aede47ef17e1e70db3d51190
>> Parent: b862815c3ee7b49ec20a9ab25da55a5f0bcbb95e
>> Refname: refs/heads/master
>> Author: Jiri Pirko <jiri@mellanox.com>
>> AuthorDate: Fri Feb 3 10:29:06 2017 +0100
>> Committer: David S. Miller <davem@davemloft.net>
>> CommitDate: Fri Feb 3 16:35:42 2017 -0500
>>
>> lib: Introduce priority array area manager
>>
>> This introduces a infrastructure for management of linear priority
>> areas. Priority order in an array matters, however order of items inside
>> a priority group does not matter.
>>
>> As an initial implementation, L-sort algorithm is used. It is quite
>> trivial. More advanced algorithm called P-sort will be introduced as a
>> follow-up. The infrastructure is prepared for other algos.
>>
>> Alongside this, a testing module is introduced as well.
>>
>> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
>> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>> --- a/lib/Kconfig
>> +++ b/lib/Kconfig
>> @@ -550,4 +550,7 @@ config STACKDEPOT
>> config SBITMAP
>> bool
>>
>> +config PARMAN
>> + tristate "parman"
>
>| parman (PARMAN) [N/m/y] (NEW) ?
>|
>| There is no help available for this option.
>
>Can you please add a description for this option?
>Or drop the "parman" string if this is always selected by its kernel users, and
>never intended to be enabled by the end user.
I did it in the same way other similar lib dependencies do that. Does
not make sense to have separate description for this, cause this is
always only a dependency of a kernel user.
You suggeste to 'drop the "parman" string'. What do you mean by that
exactly?
Thanks.
Jiri
next prev parent reply other threads:[~2017-02-23 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170222190204.878696619DE@gitolite.kernel.org>
2017-02-23 7:56 ` lib: Introduce priority array area manager Geert Uytterhoeven
2017-02-23 8:32 ` Jiri Pirko [this message]
2017-02-23 9:22 ` Geert Uytterhoeven
2017-02-23 9:25 ` Jiri Pirko
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=20170223083231.GA2699@nanopsycho \
--to=jiri@resnulli.us \
--cc=geert@linux-m68k.org \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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