All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/3 v2] Expose firmware paths via procfs
Date: Tue, 23 Oct 2012 13:52:53 +0100	[thread overview]
Message-ID: <1350996776-17864-1-git-send-email-dp@opensource.wolfsonmicro.com> (raw)

Hi Greg, I've rebased these on top of linux-next as you requested.

Dimitris Papastamos (3):
  firmware: Convert firmware path setup from an array to a list
  firmware: Add /proc/firmware_path entry to list the firmware paths
  firmware: Factor out code to add paths to the firmware path list

 drivers/base/firmware_class.c | 137 +++++++++++++++++++++++++++++++++++++++---
 1 file changed, 128 insertions(+), 9 deletions(-)

-- 
1.8.0


             reply	other threads:[~2012-10-23 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 12:52 Dimitris Papastamos [this message]
2012-10-23 12:52 ` [PATCH 1/3 v2] firmware: Convert firmware path setup from an array to a list Dimitris Papastamos
2012-10-23 13:08   ` Ming Lei
2012-10-23 13:29     ` Dimitris Papastamos
2012-10-23 13:37       ` Ming Lei
2012-10-23 13:44         ` Dimitris Papastamos
2012-10-23 14:37           ` Ming Lei
2012-10-23 12:52 ` [PATCH 2/3 v2] firmware: Add /proc/firmware_path entry to list the firmware paths Dimitris Papastamos
2012-10-25 18:48   ` Greg Kroah-Hartman
2012-10-26 10:07     ` Dimitris Papastamos
2012-10-26 23:56       ` Greg Kroah-Hartman
2012-10-23 12:52 ` [PATCH 3/3 v2] firmware: Factor out code to add paths to the firmware path list 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=1350996776-17864-1-git-send-email-dp@opensource.wolfsonmicro.com \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.