From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: linux-kernel@vger.kernel.org
Cc: Ming Lei <ming.lei@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/2] Expose firmware paths via procfs
Date: Wed, 10 Oct 2012 11:56:23 +0100 [thread overview]
Message-ID: <1349866585-24883-1-git-send-email-dp@opensource.wolfsonmicro.com> (raw)
Hi all, sorry missed the relevant CCs before. This patch set
adds support for exposing the firmware paths via procfs. I've added
an entry named /proc/fw_path which is a whitespace separated list
of firmware paths.
Once I have some time I hope to also send out a patch that allows
the user to dynamically configure these paths.
Dimitris Papastamos (2):
firmware: Convert firmware path setup from an array to a list
firmware: Add /proc/fw_path entry to list the firmware paths
drivers/base/firmware_class.c | 127 +++++++++++++++++++++++++++++++++++++++---
1 file changed, 119 insertions(+), 8 deletions(-)
--
1.7.12.2
next reply other threads:[~2012-10-10 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 10:56 Dimitris Papastamos [this message]
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
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
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=1349866585-24883-1-git-send-email-dp@opensource.wolfsonmicro.com \
--to=dp@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.