Date: Thu, 25 Oct 2012 11:48:33 -0700
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3 v2] firmware: Add /proc/firmware_path entry to list
 the firmware paths
Message-ID: <20121025184833.GA22114@kroah.com>
References: <1350996776-17864-1-git-send-email-dp@opensource.wolfsonmicro.com>
 <1350996776-17864-3-git-send-email-dp@opensource.wolfsonmicro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1350996776-17864-3-git-send-email-dp@opensource.wolfsonmicro.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 922
Lines: 26

On Tue, Oct 23, 2012 at 01:52:55PM +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.

Paths can have whitespaces :(

How about using the "universal" path seperator of ':' that shells are
used to using?  Yeah, it gets messy if you have a ':' in a path, but
from what I can tell, only the openSUSE build system does looney things
like that.

> There will be another patch on top of this that adds the functionality
> to modify the paths at runtime.

Did I miss that patch somewhere?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/