From: Boris Ostrovsky <[email protected]>
To: Jiapeng Chong <[email protected]>
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected],
Abaci Robot <[email protected]>
Subject: Re: [PATCH] x86/xen: Fix kerneldoc warning
Date: Fri, 11 Mar 2022 09:21:39 -0500 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/7/22 1:25 AM, Jiapeng Chong wrote:
> Fix the following W=1 kernel warnings:
>
> arch/x86/xen/setup.c:725: warning: expecting prototype for
> machine_specific_memory_setup(). Prototype was for xen_memory_setup()
> instead.
>
> Reported-by: Abaci Robot <[email protected]>
> Signed-off-by: Jiapeng Chong <[email protected]>
Reviewed-by: Boris Ostrovsky <[email protected]>
Applied to for-linus-5.18
prev parent reply other threads:[~2022-03-11 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 6:25 [PATCH] x86/xen: Fix kerneldoc warning Jiapeng Chong
2022-03-11 14:21 ` Boris Ostrovsky [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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