[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <8062BE1A-1674-4643-92C4-1E0A4C6E2477@linuxhacker.ru>
Date: Mon, 12 Dec 2016 23:07:53 -0500
From: Oleg Drokin <green@...uxhacker.ru>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org,
Andreas Dilger <andreas.dilger@...el.com>,
James Simmons <jsimmons@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lustre Development List <lustre-devel@...ts.lustre.org>
Subject: Re: [PATCH 0/8] Sparse warning fixes in Lustre.
On Dec 7, 2016, at 6:46 PM, Al Viro wrote:
> On Wed, Dec 07, 2016 at 05:41:26PM -0500, Oleg Drokin wrote:
>> This set of fixes aims at sparse warnings.
>
> Speaking of the stuff sparse catches there: class_process_proc_param().
> I've tried to describe what I think of that Fine Piece Of Software
> several times, but I had to give up - my command of obscenity is not
> up to the task, neither in English nor in Russian. Please, take it
> out. Preferably - along with the ->ldo_process_config()/->process_config()
> thing.
Well, I can guess what you don't like in the remnants of the
"well, we have uniform procfs, so let's use that to our advantage and simplify
or config parsing".
But what's your beef with ldo_process_config()/->process_config(), I wonder?
Just a way to propagate config info across the layers.
Powered by blists - more mailing lists