From: Thomas Gleixner <tglx@linutronix.de>
To: Shivank Garg <shivankg@amd.com>, Ingo Molnar <mingo@kernel.org>
Cc: mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, luto@kernel.org,
peterz@infradead.org, rafael@kernel.org, pavel@kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, sohil.mehta@intel.com,
rui.zhang@intel.com, yuntao.wang@linux.dev, kai.huang@intel.com,
xiaoyao.li@intel.com, peterx@redhat.com, sandipan.das@amd.com,
ak@linux.intel.com, rostedt@goodmis.org
Subject: Re: [PATCH RESEND 4/4] x86/apic: Fix W=1 build kernel-doc warning
Date: Thu, 15 May 2025 09:19:17 +0200 [thread overview]
Message-ID: <87o6vuibnu.ffs@tglx> (raw)
In-Reply-To: <51fbdbcd-a895-43b0-bb59-aa3361d77cad@amd.com>
On Thu, May 15 2025 at 12:03, Shivank Garg wrote:
> On 5/14/2025 1:26 PM, Ingo Molnar wrote:
>> This is incorrect and is based on a misunderstanding of what the code
>> does:
>>
>> DEFINE_IDTENTRY_IRQ(spurious_interrupt)
>> {
>> handle_spurious_interrupt(vector);
>> }
>
> The kernel-doc tool doesn't handle macros properly.
> Can I change it to a normal comment instead?
> or if a kernel-doc comment is required how should I make it correct?
Fix the stupid tool and leave the comment alone.
next prev parent reply other threads:[~2025-05-15 7:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 6:26 [PATCH RESEND 1/4] x86/mm: pgtable: Fix W=1 build kernel-doc warnings Shivank Garg
2025-05-14 6:26 ` [PATCH RESEND 2/4] x86/power: hibernate: " Shivank Garg
2025-05-14 6:26 ` [PATCH RESEND 3/4] x86/mm/pat: Fix W=1 build kernel-doc warning Shivank Garg
2025-05-14 6:26 ` [PATCH RESEND 4/4] x86/apic: " Shivank Garg
2025-05-14 7:56 ` Ingo Molnar
2025-05-15 6:33 ` Shivank Garg
2025-05-15 6:38 ` Ingo Molnar
2025-05-15 6:49 ` Ingo Molnar
2025-05-15 7:19 ` Thomas Gleixner [this message]
2025-05-15 8:15 ` [PATCH] x86/apic: Better document spurious_interrupt() and __spurious_interrupt() Ingo Molnar
2025-05-14 7:54 ` [PATCH RESEND 1/4] x86/mm: pgtable: Fix W=1 build kernel-doc warnings Ingo Molnar
2025-05-14 8:06 ` Shivank Garg
2025-05-14 8:27 ` Shivank Garg
2025-05-14 9:20 ` Ingo Molnar
2025-05-15 3:54 ` Shivank Garg
2025-05-15 6:54 ` Ingo Molnar
2025-05-15 9:57 ` Shivank Garg
2025-05-15 15:06 ` Ingo Molnar
2025-05-15 18:10 ` Shivank Garg
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=87o6vuibnu.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@kernel.org \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=sandipan.das@amd.com \
--cc=shivankg@amd.com \
--cc=sohil.mehta@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yuntao.wang@linux.dev \
/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