From: Bjorn Helgaas <helgaas@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
"Linux Kernel Tracing" <linux-trace-kernel@vger.kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuai Xue" <xueshuai@linux.alibaba.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Swaraj Gaikwad" <swarajgaikwad1925@gmail.com>
Subject: Re: [PATCH 0/2] PCI tracepoint documentation fixes
Date: Thu, 8 Jan 2026 10:09:16 -0600 [thread overview]
Message-ID: <20260108160916.GA485396@bhelgaas> (raw)
In-Reply-To: <20260108013956.14351-1-bagasdotme@gmail.com>
On Thu, Jan 08, 2026 at 08:39:54AM +0700, Bagas Sanjaya wrote:
> Hi,
>
> Here are two fixes for htmldocs warnings on PCI tracepoint docs as reported in
> linux-next [1]. The shortlog below should be self-explanatory.
>
> Enjoy!
>
> [1]: https://lore.kernel.org/linux-next/20260105160000.0368ec8d@canb.auug.org.au/
>
> Bagas Sanjaya (2):
> Documentation: tracing: Add toctree entry for PCI tracepoint
> Documentation: tracing: Wrap PCI tracepoint examples
>
> Documentation/trace/events-pci.rst | 4 ++--
> Documentation/trace/index.rst | 1 +
> 2 files changed, 3 insertions(+), 2 deletions(-)
These are for the pci/trace branch, which has not been merged into
mainline yet, so I squashed these fixes into the "Documentation:
tracing: Add PCI tracepoint documentation" patch on that branch.
Thanks!
Bjorn
prev parent reply other threads:[~2026-01-08 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 1:39 [PATCH 0/2] PCI tracepoint documentation fixes Bagas Sanjaya
2026-01-08 1:39 ` [PATCH 1/2] Documentation: tracing: Add toctree entry for PCI tracepoint Bagas Sanjaya
2026-01-08 4:30 ` Randy Dunlap
2026-01-08 1:39 ` [PATCH 2/2] Documentation: tracing: Wrap PCI tracepoint examples Bagas Sanjaya
2026-01-08 4:30 ` Randy Dunlap
2026-01-08 16:06 ` [PATCH 0/2] PCI tracepoint documentation fixes Steven Rostedt
2026-01-08 16:09 ` Bjorn Helgaas [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=20260108160916.GA485396@bhelgaas \
--to=helgaas@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=ilpo.jarvinen@linux.intel.com \
--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=rostedt@goodmis.org \
--cc=swarajgaikwad1925@gmail.com \
--cc=xueshuai@linux.alibaba.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