From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: broonie@kernel.org, gregkh@linuxfoundation.org
Cc: patches@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] regmap: debugfs: Allow writes to cache state settings
Date: Tue, 23 Jun 2015 14:32:53 +0100 [thread overview]
Message-ID: <1435066375-23728-1-git-send-email-rf@opensource.wolfsonmicro.com> (raw)
PATCH 1: Export the bool read/write functions from debugfs so that they can
be re-used. This is based on
/gregkh/driver-core.git : driver-core-next
PATCH 2: Allow the regmap debugfs cache state entries to be writable
This is based on:
/broonie/regmap.git : for-next
Richard Fitzgerald (2):
debugfs: Export bool read/write functions
regmap: debugfs: Allow writes to cache state settings
drivers/base/regmap/regmap-debugfs.c | 90 ++++++++++++++++++++++++++++++++--
fs/debugfs/file.c | 14 +++--
include/linux/debugfs.h | 20 ++++++++
3 files changed, 114 insertions(+), 10 deletions(-)
--
1.7.2.5
next reply other threads:[~2015-06-23 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 13:32 Richard Fitzgerald [this message]
2015-06-23 13:32 ` [PATCH v2 1/2] debugfs: Export bool read/write functions Richard Fitzgerald
2015-07-17 18:22 ` Mark Brown
2015-07-19 18:45 ` Greg KH
2015-07-20 17:52 ` Applied "debugfs: Export bool read/write functions" to the regmap tree Mark Brown
2015-08-05 20:09 ` [PATCH v2 1/2] debugfs: Export bool read/write functions Greg KH
2015-06-23 13:32 ` [PATCH v2 2/2] regmap: debugfs: Allow writes to cache state settings Richard Fitzgerald
2015-07-20 17:52 ` Applied "regmap: debugfs: Allow writes to cache state settings" to the regmap tree Mark Brown
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=1435066375-23728-1-git-send-email-rf@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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.