From: kbuild test robot <lkp@intel.com> To: Pavel Tatashin <pasha.tatashin@oracle.com> Cc: kbuild-all@01.org, pasha.tatashin@oracle.com, steven.sistare@oracle.com, daniel.m.jordan@oracle.com, linux-kernel@vger.kernel.org, jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, gregkh@linuxfoundation.org, alexander.duyck@gmail.com, tobin@apporbit.com Subject: [RFC PATCH] drivers core: device_root_tasks_done can be static Date: Sun, 6 May 2018 09:56:33 +0800 [thread overview] Message-ID: <20180506015633.GA91045@lkp-hsx03> (raw) In-Reply-To: <20180505154040.28614-2-pasha.tatashin@oracle.com> Fixes: 6d54ba128905 ("drivers core: multi-threading device shutdown") Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> --- core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/base/core.c b/drivers/base/core.c index 110d797..666c163 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -2874,7 +2874,7 @@ static int device_shutdown_child_task(void *data); */ static atomic_t device_root_tasks_finished; static atomic_t device_root_tasks_started; -struct completion device_root_tasks_done; +static struct completion device_root_tasks_done; /** * Shutdown device tree with root started in dev. If dev has no children
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com> To: intel-wired-lan@osuosl.org Subject: [Intel-wired-lan] [RFC PATCH] drivers core: device_root_tasks_done can be static Date: Sun, 6 May 2018 09:56:33 +0800 [thread overview] Message-ID: <20180506015633.GA91045@lkp-hsx03> (raw) In-Reply-To: <20180505154040.28614-2-pasha.tatashin@oracle.com> Fixes: 6d54ba128905 ("drivers core: multi-threading device shutdown") Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> --- core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/base/core.c b/drivers/base/core.c index 110d797..666c163 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -2874,7 +2874,7 @@ static int device_shutdown_child_task(void *data); */ static atomic_t device_root_tasks_finished; static atomic_t device_root_tasks_started; -struct completion device_root_tasks_done; +static struct completion device_root_tasks_done; /** * Shutdown device tree with root started in dev. If dev has no children
next prev parent reply other threads:[~2018-05-06 1:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-05 15:40 [PATCH v2 0/1] multi-threading device shutdown Pavel Tatashin 2018-05-05 15:40 ` [Intel-wired-lan] " Pavel Tatashin 2018-05-05 15:40 ` [PATCH v2 1/1] drivers core: " Pavel Tatashin 2018-05-05 15:40 ` [Intel-wired-lan] " Pavel Tatashin 2018-05-06 1:56 ` kbuild test robot 2018-05-06 1:56 ` kbuild test robot 2018-05-06 1:56 ` kbuild test robot [this message] 2018-05-06 1:56 ` [Intel-wired-lan] [RFC PATCH] drivers core: device_root_tasks_done can be static kbuild test robot 2018-05-23 10:40 ` [PATCH v2 1/1] drivers core: multi-threading device shutdown Pavel Machek 2018-05-23 10:40 ` [Intel-wired-lan] " Pavel Machek 2018-05-23 11:31 ` Pavel Tatashin 2018-05-23 11:31 ` [Intel-wired-lan] " Pavel Tatashin
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=20180506015633.GA91045@lkp-hsx03 \ --to=lkp@intel.com \ --cc=alexander.duyck@gmail.com \ --cc=daniel.m.jordan@oracle.com \ --cc=gregkh@linuxfoundation.org \ --cc=intel-wired-lan@lists.osuosl.org \ --cc=jeffrey.t.kirsher@intel.com \ --cc=kbuild-all@01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=pasha.tatashin@oracle.com \ --cc=steven.sistare@oracle.com \ --cc=tobin@apporbit.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: linkBe 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.