mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zouwei (Samuel)" <zou_wei@huawei.com>
To: Hans de Goede <hdegoede@redhat.com>,
	"justin.ernst@hpe.com" <justin.ernst@hpe.com>,
	"mgross@linux.intel.com" <mgross@linux.intel.com>
Cc: "platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>
Subject: 答复: [PATCH -next] x86/platform/uv: Mark some symbols with static keyword
Date: Tue, 1 Dec 2020 11:12:22 +0000	[thread overview]
Message-ID: <1bdf4b73d97f4671a69183d1028a0aae@huawei.com> (raw)
In-Reply-To: <55abc980-2493-5c29-da80-4bb1446fa37d@redhat.com>

Hi,

Please help to pick it up after 5.11-rc1, thanks a lot.

-----邮件原件-----
发件人: Hans de Goede [mailto:hdegoede@redhat.com] 
发送时间: 2020年11月30日 21:31
收件人: Zouwei (Samuel) <zou_wei@huawei.com>; justin.ernst@hpe.com; mgross@linux.intel.com
抄送: platform-driver-x86@vger.kernel.org; linux-kernel@vger.kernel.org; x86@kernel.org
主题: Re: [PATCH -next] x86/platform/uv: Mark some symbols with static keyword

Hi,

+Cc x86 folks

On 11/30/20 12:11 PM, Zou Wei wrote:
> Fix the following sparse warnings:
> 
> drivers/platform/x86/uv_sysfs.c:22:13: warning: symbol 'uv_pcibus_kset' was not declared. Should it be static?
> drivers/platform/x86/uv_sysfs.c:23:13: warning: symbol 'uv_hubs_kset' was not declared. Should it be static?
> 
> Signed-off-by: Zou Wei <zou_wei@huawei.com>

Since this is a fix to a series merged through the x86/tip tree, this should be merged to the x86/tip tree too (or I can pick it up after 5.11-rc1).

Here is my ack for merging this through the x86/tip tree:

Acked-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans



> ---
>  drivers/platform/x86/uv_sysfs.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/platform/x86/uv_sysfs.c 
> b/drivers/platform/x86/uv_sysfs.c index 54c3425..c780a4b 100644
> --- a/drivers/platform/x86/uv_sysfs.c
> +++ b/drivers/platform/x86/uv_sysfs.c
> @@ -19,8 +19,8 @@
>  #define INVALID_CNODE -1
>  
>  struct kobject *sgi_uv_kobj;
> -struct kset *uv_pcibus_kset;
> -struct kset *uv_hubs_kset;
> +static struct kset *uv_pcibus_kset;
> +static struct kset *uv_hubs_kset;
>  static struct uv_bios_hub_info *hub_buf;  static struct 
> uv_bios_port_info **port_buf;  static struct uv_hub **uv_hubs;
> 


  reply	other threads:[~2020-12-01 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 11:11 Zou Wei
2020-11-30 13:30 ` Hans de Goede
2020-12-01 11:12   ` Zouwei (Samuel) [this message]
2020-12-03  8:01 ` [tip: x86/platform] x86/platform/uv: Make uv_pcibus_kset and uv_hubs_kset static tip-bot2 for Zou Wei

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=1bdf4b73d97f4671a69183d1028a0aae@huawei.com \
    --to=zou_wei@huawei.com \
    --cc=hdegoede@redhat.com \
    --cc=justin.ernst@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=x86@kernel.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

Powered by JetHome