From: Steven Rostedt <rostedt@goodmis.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
mark.rutland@arm.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentaion:trace Add the git web link to view it on the browser
Date: Tue, 5 Dec 2023 11:26:08 -0500 [thread overview]
Message-ID: <20231205112608.76927866@gandalf.local.home> (raw)
In-Reply-To: <20231205035517.30534-1-unixbhaskar@gmail.com>
On Tue, 5 Dec 2023 09:25:17 +0530
Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
> Thought this might help people to see the entire source tree on browser and
> explore.
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Documentation/trace/ftrace.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index 23572f6697c0..e768a4c91452 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -3731,3 +3731,5 @@ Currently, -mfentry is used by gcc 4.6.0 and above on x86 only.
> More
> ----
> More details can be found in the source code, in the `kernel/trace/*.c` files.
> +Also you can see the trace source tree on browser `Git Link
> +<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/trace>`__.
> --
> 2.35.8
I'm not a big fan of git links to code in the documentation tree. This is
more for those that want to play with it (compile and install), so I don't
think a web link is useful here. I rather have people download the code and
build it.
-- Steve
prev parent reply other threads:[~2023-12-05 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 3:55 [PATCH] Documentaion:trace Add the git web link to view it on the browser Bhaskar Chowdhury
2023-12-05 16:26 ` Steven Rostedt [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=20231205112608.76927866@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=unixbhaskar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox