From: Jacob Keller <jacob.e.keller@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: kdoc: fix duplicate section warning message
Date: Thu, 30 Oct 2025 08:44:48 -0700 [thread overview]
Message-ID: <1c23850b-eb67-4ee8-ab1b-2e4d8999bbaf@intel.com> (raw)
In-Reply-To: <f226af11-adbb-444f-9322-1dd3116321f7@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 847 bytes --]
On 10/29/2025 1:39 PM, Randy Dunlap wrote:
> On 10/29/25 1:04 PM, Jacob Keller wrote:
>>> We'll have to see if Mauro already has a fix for this. (I reported
>>> it a couple of weeks ago.)
>>
>> I searched mail archives but didn't find a report, so hence the patch.
>> If this already has a proper fix thats fine.
>>
>
> It was discussed here and Mauro said that he sent a patch but I still
> see those warnings in linux-next-20251029.
>
> https://lore.kernel.org/all/jd5uf3ud2khep2oqyos3uhfkuptvcm4zgboelfxjut43bxpr6o@ye24ej7g3p7n/
>
Thanks. I don't see any fix from him on the Lore archives, and I don't
see one on linux-next or docs-next, but at least its obvious Mauro is
aware of the issue.
Either way, we can wait for Mauro's response here and take or leave this
patch, whichever way he prefers.
Regards,
Jake
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-10-30 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 18:30 [PATCH] docs: kdoc: fix duplicate section warning message Jacob Keller
2025-10-29 19:45 ` Randy Dunlap
2025-10-29 20:04 ` Jacob Keller
2025-10-29 20:16 ` Jacob Keller
2025-10-29 20:39 ` Randy Dunlap
2025-10-30 15:44 ` Jacob Keller [this message]
2025-10-30 16:54 ` Jonathan Corbet
2025-10-30 19:47 ` Jacob Keller
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=1c23850b-eb67-4ee8-ab1b-2e4d8999bbaf@intel.com \
--to=jacob.e.keller@intel.com \
--cc=corbet@lwn.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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).