From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux PM <linux-pm@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v1] smp: Fix up and expand the smp_call_function_many() kerneldoc
Date: Thu, 18 Sep 2025 10:31:06 +0200 [thread overview]
Message-ID: <87h5x088mt.ffs@tglx> (raw)
In-Reply-To: <CAJZ5v0gEh-xoKdgAgUvnGzPV6AO51=ZagHXNCrC4BfRZk6Oydw@mail.gmail.com>
On Tue, Sep 16 2025 at 16:13, Rafael J. Wysocki wrote:
> On Tue, Sep 9, 2025 at 1:44 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>>
>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>
>> The smp_call_function_many() kerneldoc comment got out of sync with the
>> function definition (bool parameter "wait" is incorrectly described as a
>> bitmask in it), so fix it up by copying the "wait" description from the
>> smp_call_function() kerneldoc and add information regarding the handling
>> of the local CPU to it.
>>
>> Fixes: 49b3bd213a9f ("smp: Fix all kernel-doc warnings")
>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> It's been a week and no feedback.
>
> Well, in the further absence of any, I'll assume no concerns and just
> queue this up.
Sorry, was distracted. No objections from my side. Did you queue it
already?
next prev parent reply other threads:[~2025-09-18 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 11:44 [PATCH v1] smp: Fix up and expand the smp_call_function_many() kerneldoc Rafael J. Wysocki
2025-09-16 14:13 ` Rafael J. Wysocki
2025-09-18 8:31 ` Thomas Gleixner [this message]
2025-09-18 10:05 ` Rafael J. Wysocki
2025-09-18 20:17 ` Thomas Gleixner
2025-09-18 20:19 ` Rafael J. Wysocki
2025-09-18 20:25 ` [tip: smp/core] " tip-bot2 for Rafael J. Wysocki
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=87h5x088mt.ffs@tglx \
--to=tglx@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@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 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.