summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/debugfs.txt
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2015-09-27 00:04:07 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-10-04 12:36:07 +0200
commit621a5f7ad9cd1ce7933f1d302067cbd58354173c (patch)
treea9cd51d4b4e70286a339ffc463618d0f33279c67 /Documentation/filesystems/debugfs.txt
parentACPI / EC: Fix broken 64bit big-endian users of 'global_lock' (diff)
downloadlinux-621a5f7ad9cd1ce7933f1d302067cbd58354173c.tar.xz
linux-621a5f7ad9cd1ce7933f1d302067cbd58354173c.zip
debugfs: Pass bool pointer to debugfs_create_bool()
Its a bit odd that debugfs_create_bool() takes 'u32 *' as an argument, when all it needs is a boolean pointer. It would be better to update this API to make it accept 'bool *' instead, as that will make it more consistent and often more convenient. Over that bool takes just a byte. That required updates to all user sites as well, in the same commit updating the API. regmap core was also using debugfs_{read|write}_file_bool(), directly and variable types were updated for that to be bool as well. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Mark Brown <broonie@kernel.org> Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/filesystems/debugfs.txt')
-rw-r--r--Documentation/filesystems/debugfs.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/filesystems/debugfs.txt b/Documentation/filesystems/debugfs.txt
index 463f595733e8..4f45f71149cb 100644
--- a/Documentation/filesystems/debugfs.txt
+++ b/Documentation/filesystems/debugfs.txt
@@ -105,7 +105,7 @@ a variable of type size_t.
Boolean values can be placed in debugfs with:
struct dentry *debugfs_create_bool(const char *name, umode_t mode,
- struct dentry *parent, u32 *value);
+ struct dentry *parent, bool *value);
A read on the resulting file will yield either Y (for non-zero values) or
N, followed by a newline. If written to, it will accept either upper- or