From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Samuel Zou <zou_wei@huawei.com>,
jpoimboe@redhat.com, jikos@kernel.org, mbenes@suse.cz,
pmladek@suse.com, joe.lawrence@redhat.com
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] livepatch: Make klp_apply_object_relocs static
Date: Fri, 8 May 2020 20:04:56 +0530 [thread overview]
Message-ID: <452d206f-4d4f-747f-be34-76fc3c09f780@linux.vnet.ibm.com> (raw)
In-Reply-To: <1588939594-58255-1-git-send-email-zou_wei@huawei.com>
On 5/8/20 5:36 PM, Samuel Zou wrote:
> Fix the following sparse warning:
>
> kernel/livepatch/core.c:748:5: warning: symbol 'klp_apply_object_relocs'
> was not declared. Should it be static?
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Samuel Zou <zou_wei@huawei.com>
LGTM, klp_apply_object_relocs() has only one call site within core.c
Reviewed-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> ---
> kernel/livepatch/core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/livepatch/core.c b/kernel/livepatch/core.c
> index 96d2da1..f76fdb9 100644
> --- a/kernel/livepatch/core.c
> +++ b/kernel/livepatch/core.c
> @@ -745,7 +745,8 @@ static int klp_init_func(struct klp_object *obj, struct klp_func *func)
> func->old_sympos ? func->old_sympos : 1);
> }
>
> -int klp_apply_object_relocs(struct klp_patch *patch, struct klp_object *obj)
> +static int klp_apply_object_relocs(struct klp_patch *patch,
> + struct klp_object *obj)
> {
> int i, ret;
> struct klp_modinfo *info = patch->mod->klp_info;
>
next prev parent reply other threads:[~2020-05-08 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 12:06 [PATCH -next] livepatch: Make klp_apply_object_relocs static Samuel Zou
2020-05-08 14:34 ` Kamalesh Babulal [this message]
2020-05-08 15:53 ` Josh Poimboeuf
2020-05-08 15:55 ` Josh Poimboeuf
2020-05-09 0:38 ` Samuel Zou
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=452d206f-4d4f-747f-be34-76fc3c09f780@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=zou_wei@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox