From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: Minor fixes
Date: Fri, 04 May 2018 11:52:41 -0400 [thread overview]
Message-ID: <20180504155241.113624273@goodmis.org> (raw)
Linus,
Some of the files in the tracing directory show file mode 0444
when they are writable by root. To fix the confusion, they should
be 0644. Note, either case root can still write to them.
Note, Zhengyuan asked why I never applied that patch (the first one
is from 2014!). I simply forgot about it. /me lowers head in shame.
Please pull the latest trace-v4.17-rc1-3 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.17-rc1-3
Tag SHA1: b23eed18b73241c8aa5829cc6f570610ce65c93b
Head SHA1: 0c5a9acc8b4e878e761f735e144d4a7e4477d4e6
Chen LinX (1):
ftrace: Have set_graph_* files have normal file modes
Zhengyuan Liu (1):
tracing: Fix the file mode of stack tracer
----
kernel/trace/ftrace.c | 4 ++--
kernel/trace/trace_stack.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2018-05-04 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 15:52 Steven Rostedt [this message]
2018-05-04 15:52 ` [PATCH 1/2] ftrace: Have set_graph_* files have normal file modes Steven Rostedt
2018-05-04 15:52 ` [PATCH 2/2] tracing: Fix the file mode of stack tracer Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2013-02-19 4:15 [PATCH 0/2] [GIT PULL] tracing: minor fixes Steven Rostedt
2010-10-21 2:42 [PATCH 0/2] [GIT PULL] tracing: Minor fixes Steven Rostedt
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=20180504155241.113624273@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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