From: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: "Anil S Keshavamurthy" <anil.s.keshavamurthy@intel.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Daniel Bristot de Oliveira" <bristot@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
"Greg\
Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jens Wiklander" <jens.wiklander@linaro.org>,
"Lecopzer Chen" <lecopzer.chen@mediatek.com>,
linux-arch@vger.kernel.org,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
"Sameer\
Rahmani" <lxsameer@gnu.org>, "Ingo Molnar" <mingo@kernel.org>,
"Ohad Ben-Cohen" <ohad@wizery.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Rob Herring" <robh@kernel.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
tee-dev@lists.linaro.org, "Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH 12/14] docs: move remaining stuff under Documentation/*.txt to Documentation/staging
Date: Mon, 04 May 2020 15:21:53 +0530 [thread overview]
Message-ID: <1588585777.904qzycqcn.naveen@linux.ibm.com> (raw)
In-Reply-To: <20200504085415.db8e0e3b40e795f2fb4af009@kernel.org>
Masami Hiramatsu wrote:
> On Fri, 1 May 2020 17:37:56 +0200
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
>
>> There are several files that I was unable to find a proper place
>> for them, and 3 ones that are still in plain old text format.
>>
>> Let's place those stuff behind the carpet, as we'd like to keep the
>> root directory clean.
>>
>> We can later discuss and move those into better places.
>
> Hi Mauro,
>
> Thanks for cleaning it up! Tentatively moving kprobes.txt under
> staging/ is good to me.
>
> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
>
> BTW, I think kprobes.txt is under trace/ or we may be better
> making a new core-api/events/ directory and prepare other event
> systems (PMU, uprobes, and hw_breakpoint.)
I think it would be good to move kprobes.txt under trace/ -- all other
tracing bits are already present there, including uprobes.
- Naveen
prev parent reply other threads:[~2020-05-04 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1588345503.git.mchehab+huawei@kernel.org>
2020-05-01 15:37 ` [PATCH 10/14] docs: move locking-specific documenta to locking/ directory Mauro Carvalho Chehab
2020-05-15 18:06 ` Jonathan Corbet
2020-05-22 4:39 ` Mauro Carvalho Chehab
2020-05-01 15:37 ` [PATCH 12/14] docs: move remaining stuff under Documentation/*.txt to Documentation/staging Mauro Carvalho Chehab
2020-05-03 23:54 ` Masami Hiramatsu
2020-05-04 0:47 ` Joe Perches
2020-05-04 9:51 ` Naveen N. Rao [this message]
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=1588585777.904qzycqcn.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=bristot@redhat.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.org \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lxsameer@gnu.org \
--cc=mchehab+huawei@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=ohad@wizery.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tee-dev@lists.linaro.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).