From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751346AbdBWIdS (ORCPT ); Thu, 23 Feb 2017 03:33:18 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:36724 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169AbdBWIcy (ORCPT ); Thu, 23 Feb 2017 03:32:54 -0500 Date: Thu, 23 Feb 2017 09:32:31 +0100 From: Jiri Pirko To: Geert Uytterhoeven Cc: Jiri Pirko , "netdev@vger.kernel.org" , Linux Kernel Mailing List Subject: Re: lib: Introduce priority array area manager Message-ID: <20170223083231.GA2699@nanopsycho> References: <20170222190204.878696619DE@gitolite.kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > wrote: >> Web: https://git.kernel.org/torvalds/c/44091d29f2075972aede47ef17e1e70db3d51190 >> Commit: 44091d29f2075972aede47ef17e1e70db3d51190 >> Parent: b862815c3ee7b49ec20a9ab25da55a5f0bcbb95e >> Refname: refs/heads/master >> Author: Jiri Pirko >> AuthorDate: Fri Feb 3 10:29:06 2017 +0100 >> Committer: David S. Miller >> 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 >> Signed-off-by: David S. Miller > >> --- 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