From: jim.cromie@gmail.com
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
gregkh@linuxfoundation.org, jbaron@akamai.com,
ukaszb@chromium.org, louis.chauvet@bootlin.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 31/31] docs/dyndbg: add classmap info to howto
Date: Thu, 20 Nov 2025 09:22:15 -0700 [thread overview]
Message-ID: <CAJfuBxxKM_4nxm3YLeCqiDpb5TBB_Hrx0UWOtASTRLBbKmH6Og@mail.gmail.com> (raw)
In-Reply-To: <aR6GQeLW-sh9-A3W@archie.me>
On Wed, Nov 19, 2025 at 8:08 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On Tue, Nov 18, 2025 at 01:18:41PM -0700, Jim Cromie wrote:
> > diff --git a/Documentation/admin-guide/dynamic-debug-howto.rst b/Documentation/admin-guide/dynamic-debug-howto.rst
...
>
> Hmmm... the resulting htmldocs looks messy so I clean it up:
>
thank you.
Ive absorbed your fixes into my copy.
next prev parent reply other threads:[~2025-11-20 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251118201842.1447666-1-jim.cromie@gmail.com>
2025-11-18 20:18 ` [PATCH v6 04/31] docs/dyndbg: explain flags parse 1st Jim Cromie
2025-11-20 9:30 ` Bagas Sanjaya
2025-11-18 20:18 ` [PATCH v6 21/31] dyndbg-API: replace DECLARE_DYNDBG_CLASSMAP Jim Cromie
2025-11-18 20:18 ` [PATCH v6 25/31] dyndbg-API: promote DYNAMIC_DEBUG_CLASSMAP_PARAM to API Jim Cromie
2025-11-18 20:18 ` [PATCH v6 31/31] docs/dyndbg: add classmap info to howto Jim Cromie
2025-11-20 3:08 ` Bagas Sanjaya
2025-11-20 16:22 ` jim.cromie [this message]
[not found] ` <20251118201842.1447666-17-jim.cromie@gmail.com>
[not found] ` <fcb2532d-5627-4bc3-a990-ed361b56ccd3@akamai.com>
2025-12-10 6:33 ` [PATCH v6 16/31] dyndbg: hoist classmap-filter-by-modname up to ddebug_add_module jim.cromie
2025-12-10 19:14 ` Jason Baron
2025-12-10 20:21 ` jim.cromie
2025-12-12 16:05 ` Jason Baron
2025-12-14 18:09 ` jim.cromie
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=CAJfuBxxKM_4nxm3YLeCqiDpb5TBB_Hrx0UWOtASTRLBbKmH6Og@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=ukaszb@chromium.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).