linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Purva Yeshi <purvayeshi550@gmail.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] docs: tracing: Reduce maxdepth in index documentation
Date: Thu, 13 Mar 2025 19:16:17 +0700	[thread overview]
Message-ID: <4cc0a072-3eaf-4fbf-a334-012aacf9039f@gmail.com> (raw)
In-Reply-To: <20250313070457.647c8c57@batman.local.home>

On 3/13/25 18:04, Steven Rostedt wrote:
> On Thu, 13 Mar 2025 10:02:01 +0700
> Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> 
>> If you'd like to generate a patch series, you can refer to thoughtbot
>> blogpost at [1].
> 
> ??
> 
> This is already a patch series.
> 
>>
>> And you can also add cover letter by passing --cover-letter to
>> git-format-patch(1).
> 
> It's simple enough it doesn't need a cover letter.
> 

I mean I'm directing my reply to Purva.

Thanks anyway.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2025-03-13 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 12:47 [PATCH v3 2/2] docs: tracing: Reduce maxdepth in index documentation Purva Yeshi
2025-03-12 17:49 ` Steven Rostedt
2025-03-13  3:02   ` Bagas Sanjaya
2025-03-13 11:04     ` Steven Rostedt
2025-03-13 12:16       ` Bagas Sanjaya [this message]
2025-03-14  8:56         ` Purva Yeshi
2025-03-14 12:41           ` Steven Rostedt
2025-03-18 11:35             ` Purva Yeshi
2025-03-14  8:55   ` Purva Yeshi
2025-03-14 12:35     ` 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=4cc0a072-3eaf-4fbf-a334-012aacf9039f@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=purvayeshi550@gmail.com \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).