| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20121026235649.GB13263@kroah.com> Date: Fri, 26 Oct 2012 16:56:49 -0700 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Dimitris Papastamos <dp@...nsource.wolfsonmicro.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/3 v2] firmware: Add /proc/firmware_path entry to list the firmware paths On Fri, Oct 26, 2012 at 11:07:31AM +0100, Dimitris Papastamos wrote: > On Thu, Oct 25, 2012 at 11:48:33AM -0700, Greg Kroah-Hartman wrote: > > 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. > > Sure I can do that, however, could you comment on Ming's comments? Is > this patchset something we find useful at the moment as regards listing > and/or updating the firmware path list. I really don't remember anymore, sorry. That was a few hunderd or so patches ago that I've reviewed... greg k-h -- 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