From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, Ming Lei <ming.lei@canonical.com>
Subject: Re: [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths
Date: Wed, 10 Oct 2012 22:36:55 +0900 [thread overview]
Message-ID: <20121010133655.GA11678@kroah.com> (raw)
In-Reply-To: <1349866585-24883-3-git-send-email-dp@opensource.wolfsonmicro.com>
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@opensource.wolfsonmicro.com>
What about /proc/sys/kernel/firmware_path instead? Isn't that a better
place for this?
greg k-h
next prev parent reply other threads:[~2012-10-10 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 10:56 [PATCH 0/2] Expose firmware paths via procfs Dimitris Papastamos
2012-10-10 10:56 ` [PATCH 1/2] firmware: Convert firmware path setup from an array to a list Dimitris Papastamos
2012-10-22 15:42 ` Greg Kroah-Hartman
2012-10-23 9:43 ` Dimitris Papastamos
2012-10-10 10:56 ` [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths Dimitris Papastamos
2012-10-10 13:36 ` Greg Kroah-Hartman [this message]
2012-10-10 13:40 ` Josh Boyer
2012-10-10 13:45 ` Dimitris Papastamos
2012-10-10 14:41 ` Dimitris Papastamos
2012-10-10 15:14 ` [PATCH 0/2] Expose firmware paths via procfs Ming Lei
-- strict thread matches above, loose matches on Subject: below --
2012-10-09 22:50 [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths Dimitris Papastamos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121010133655.GA11678@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox