All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Knop, Ryszard" <ryszard.knop@intel.com>
To: "corbet@lwn.net" <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Lin, Shuicheng" <shuicheng.lin@intel.com>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts/kernel-doc: Suggest possible names for excess descriptions
Date: Fri, 17 Jul 2026 13:07:17 +0000	[thread overview]
Message-ID: <bc201789fb00c339971fee35c046e9f0b59dcb6d.camel@intel.com> (raw)
In-Reply-To: <87tspy5zjy.fsf@trenco.lwn.net>

On Thu, 2026-07-16 at 16:40 -0600, Jonathan Corbet wrote:
> Ryszard Knop <ryszard.knop@intel.com> writes:
> 
> > Since check_sections() now warns if a documentation tag member name is
> > the same as defined in the struct, we can suggest names the checker
> > knows, so that it's more obvious how to deal with the warning.
> > 
> > Signed-off-by: Ryszard Knop <ryszard.knop@intel.com>
> > ---
> >  tools/lib/python/kdoc/kdoc_parser.py | 13 +++++++++++--
> >  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> So I almost applied this version of this patch.  For future reference,
> please:
> 
> - Post new versions standalone, not as a reply
> 
> - Do not include version information in the changelog (put it below the
>   "---" line)
> 
> - Provide a more coherent changelog; the one above does not say what is
>   actually going on here.
> 
> - CC the maintainer (me).

Submitted a v3 with changes Mauro requested, fixed changelog and CC'd,
but accidentally sent it again with In-Reply-To which I had in the
command last time, sorry :/

> 
> Thanks,
> 
> jon

Thanks, Ryszard

  reply	other threads:[~2026-07-17 13:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 11:12 [PATCH] scripts/kernel-doc: Suggest possible names for excess descriptions Ryszard Knop
2026-07-14 12:21 ` ✓ CI.KUnit: success for " Patchwork
2026-07-14 13:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-14 18:12 ` ✓ Xe.CI.FULL: " Patchwork
2026-07-14 21:44 ` [PATCH] " Randy Dunlap
2026-07-15 11:18   ` Knop, Ryszard
2026-07-15 11:17 ` [PATCH v2] " Ryszard Knop
2026-07-15 12:42   ` Mauro Carvalho Chehab
2026-07-15 13:21     ` Knop, Ryszard
2026-07-15 13:52       ` Mauro Carvalho Chehab
2026-07-17 13:17         ` Knop, Ryszard
2026-07-15 12:39 ` ✓ CI.KUnit: success for scripts/kernel-doc: Suggest possible names for excess descriptions (rev2) Patchwork
2026-07-15 13:19 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-15 15:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-07-16 22:40 ` [PATCH] scripts/kernel-doc: Suggest possible names for excess descriptions Jonathan Corbet
2026-07-17 13:07   ` Knop, Ryszard [this message]
2026-07-17 12:57 ` [PATCH v3] " Ryszard Knop
2026-07-17 16:28   ` Randy Dunlap
2026-07-22 16:15   ` Jonathan Corbet
2026-07-31  3:19   ` Akira Yokosawa
2026-07-31 14:45     ` Knop, Ryszard
2026-07-17 13:05 ` ✓ CI.KUnit: success for scripts/kernel-doc: Suggest possible names for excess descriptions (rev3) Patchwork
2026-07-17 13:41 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-17 20:21 ` ✓ Xe.CI.FULL: " Patchwork

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=bc201789fb00c339971fee35c046e9f0b59dcb6d.camel@intel.com \
    --to=ryszard.knop@intel.com \
    --cc=corbet@lwn.net \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=shuicheng.lin@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.