From: Stephen Boyd <sboyd@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/4] Consolidate debugfs mode checks in creation APIs
Date: Mon, 12 Oct 2015 18:09:08 -0700 [thread overview]
Message-ID: <1444698552-12369-1-git-send-email-sboyd@codeaurora.org> (raw)
Reviewing Viresh's patch it looks like there was some ample
opportunity to consolidate code here, and also close some
holes where variables are modifiable. Split into multiple
patches in case something causes regressions.
Stephen Boyd (4):
debugfs: Consolidate file mode checks in debugfs_create_*()
debugfs: Add read-only/write-only x64 file ops
debugfs: Add read-only/write-only size_t file ops
debugfs: Add read-only/write-only bool file ops
fs/debugfs/file.c | 123 ++++++++++++++++++++++++------------------------------
1 file changed, 54 insertions(+), 69 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2015-10-13 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 1:09 Stephen Boyd [this message]
2015-10-13 1:09 ` [PATCH 1/4] debugfs: Consolidate file mode checks in debugfs_create_*() Stephen Boyd
2015-10-13 3:43 ` Viresh Kumar
2015-10-13 1:09 ` [PATCH 2/4] debugfs: Add read-only/write-only x64 file ops Stephen Boyd
2015-10-13 3:44 ` Viresh Kumar
2015-10-13 1:09 ` [PATCH 3/4] debugfs: Add read-only/write-only size_t " Stephen Boyd
2015-10-13 3:45 ` Viresh Kumar
2015-10-13 1:09 ` [PATCH 4/4] debugfs: Add read-only/write-only bool " Stephen Boyd
2015-10-13 3:46 ` Viresh Kumar
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=1444698552-12369-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox