[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 10 Oct 2012 09:40:23 -0400
From: Josh Boyer <jwboyer@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
linux-kernel@...r.kernel.org, Ming Lei <ming.lei@...onical.com>
Subject: Re: [PATCH 2/2] firmware: Add /proc/fw_path entry to list the
firmware paths
On Wed, Oct 10, 2012 at 9:36 AM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Wed, Oct 10, 2012 at 11:56:25AM +0100, Dimitris Papastamos wrote:
>> This patch provides the aforementioned procfs file that lists
>> the default firmware paths that are used during firmware lookup.
>>
>> The file contains a white space separated list of paths.
>>
>> There will be another patch on top of this that adds the functionality
>> to modify the paths at runtime.
>>
>> Signed-off-by: Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>
>
> What about /proc/sys/kernel/firmware_path instead? Isn't that a better
> place for this?
Without painting the bikeshed too many colors, I was wondering if /proc
was the right place for this at all. Perhaps /sys/kernel/firmware_path
or /sys/firmware/firmware_path?
josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists