From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhi.wang.linux@gmail.com>,
hch@lst.de, jgg@nvidia.com, jani.nikula@linux.intel.com
Cc: kbuild-all@lists.01.org, Zhi Wang <zhi.wang.linux@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Terrence Xu <terrence.xu@intel.com>,
intel-gvt-dev@lists.freedesktop.org
Subject: [RFC PATCH] i915/gvt: intel_gvt_match_device() can be static
Date: Fri, 28 Jan 2022 13:01:11 +0800 [thread overview]
Message-ID: <20220128050111.GA69282@e2c1dfe2c692> (raw)
In-Reply-To: <20220127120508.11330-1-zhi.a.wang@intel.com>
drivers/gpu/drm/i915/gvt/handlers.c:45:6: warning: symbol 'intel_gvt_match_device' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
handlers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
index dad31ad074a03..459f0d902f64f 100644
--- a/drivers/gpu/drm/i915/gvt/handlers.c
+++ b/drivers/gpu/drm/i915/gvt/handlers.c
@@ -42,7 +42,7 @@
#include "display/intel_display_types.h"
#include "display/intel_fbc.h"
-bool intel_gvt_match_device(struct intel_gvt *gvt,
+static bool intel_gvt_match_device(struct intel_gvt *gvt,
unsigned long device)
{
return intel_gvt_get_device_type(gvt->gt->i915) & device;
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhi.wang.linux@gmail.com>,
hch@lst.de, jgg@nvidia.com, jani.nikula@linux.intel.com
Cc: kbuild-all@lists.01.org, Zhi Wang <zhi.wang.linux@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org
Subject: [RFC PATCH] i915/gvt: intel_gvt_match_device() can be static
Date: Fri, 28 Jan 2022 13:01:11 +0800 [thread overview]
Message-ID: <20220128050111.GA69282@e2c1dfe2c692> (raw)
In-Reply-To: <20220127120508.11330-1-zhi.a.wang@intel.com>
drivers/gpu/drm/i915/gvt/handlers.c:45:6: warning: symbol 'intel_gvt_match_device' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
handlers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
index dad31ad074a03..459f0d902f64f 100644
--- a/drivers/gpu/drm/i915/gvt/handlers.c
+++ b/drivers/gpu/drm/i915/gvt/handlers.c
@@ -42,7 +42,7 @@
#include "display/intel_display_types.h"
#include "display/intel_fbc.h"
-bool intel_gvt_match_device(struct intel_gvt *gvt,
+static bool intel_gvt_match_device(struct intel_gvt *gvt,
unsigned long device)
{
return intel_gvt_get_device_type(gvt->gt->i915) & device;
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhi.wang.linux@gmail.com>,
hch@lst.de, jgg@nvidia.com, jani.nikula@linux.intel.com
Cc: kbuild-all@lists.01.org, Zhi Wang <zhi.wang.linux@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Terrence Xu <terrence.xu@intel.com>,
intel-gvt-dev@lists.freedesktop.org
Subject: [Intel-gfx] [RFC PATCH] i915/gvt: intel_gvt_match_device() can be static
Date: Fri, 28 Jan 2022 13:01:11 +0800 [thread overview]
Message-ID: <20220128050111.GA69282@e2c1dfe2c692> (raw)
In-Reply-To: <20220127120508.11330-1-zhi.a.wang@intel.com>
drivers/gpu/drm/i915/gvt/handlers.c:45:6: warning: symbol 'intel_gvt_match_device' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
handlers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
index dad31ad074a03..459f0d902f64f 100644
--- a/drivers/gpu/drm/i915/gvt/handlers.c
+++ b/drivers/gpu/drm/i915/gvt/handlers.c
@@ -42,7 +42,7 @@
#include "display/intel_display_types.h"
#include "display/intel_fbc.h"
-bool intel_gvt_match_device(struct intel_gvt *gvt,
+static bool intel_gvt_match_device(struct intel_gvt *gvt,
unsigned long device)
{
return intel_gvt_get_device_type(gvt->gt->i915) & device;
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] i915/gvt: intel_gvt_match_device() can be static
Date: Fri, 28 Jan 2022 13:01:11 +0800 [thread overview]
Message-ID: <20220128050111.GA69282@e2c1dfe2c692> (raw)
In-Reply-To: <20220127120508.11330-1-zhi.a.wang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
drivers/gpu/drm/i915/gvt/handlers.c:45:6: warning: symbol 'intel_gvt_match_device' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
handlers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
index dad31ad074a03..459f0d902f64f 100644
--- a/drivers/gpu/drm/i915/gvt/handlers.c
+++ b/drivers/gpu/drm/i915/gvt/handlers.c
@@ -42,7 +42,7 @@
#include "display/intel_display_types.h"
#include "display/intel_fbc.h"
-bool intel_gvt_match_device(struct intel_gvt *gvt,
+static bool intel_gvt_match_device(struct intel_gvt *gvt,
unsigned long device)
{
return intel_gvt_get_device_type(gvt->gt->i915) & device;
next prev parent reply other threads:[~2022-01-28 5:02 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 12:05 [PATCH 1/3] i915/gvt: Introduce the mmio_table.c to support VFIO new mdev API Zhi Wang
2022-01-27 12:05 ` [Intel-gfx] " Zhi Wang
2022-01-27 12:05 ` Zhi Wang
2022-01-27 12:05 ` [PATCH 2/3] i915/gvt: save the initial HW state snapshot in i915 Zhi Wang
2022-01-27 12:05 ` [Intel-gfx] " Zhi Wang
2022-01-27 12:05 ` Zhi Wang
2022-01-31 6:38 ` Christoph Hellwig
2022-01-31 6:38 ` [Intel-gfx] " Christoph Hellwig
2022-01-27 12:05 ` [PATCH 3/3] i915/gvt: Use the initial HW state snapshot saved " Zhi Wang
2022-01-27 12:05 ` [Intel-gfx] " Zhi Wang
2022-01-27 12:05 ` Zhi Wang
2022-01-27 14:52 ` [PATCH 1/3] i915/gvt: Introduce the mmio_table.c to support VFIO new mdev API Christoph Hellwig
2022-01-27 14:52 ` [Intel-gfx] " Christoph Hellwig
2022-01-27 15:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] " Patchwork
2022-01-27 15:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-27 15:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-27 17:14 ` [Intel-gfx] [PATCH 1/3] " kernel test robot
2022-01-27 17:14 ` kernel test robot
2022-01-27 17:14 ` kernel test robot
2022-01-27 17:46 ` kernel test robot
2022-01-27 17:46 ` kernel test robot
2022-01-27 17:46 ` kernel test robot
2022-01-27 17:46 ` kernel test robot
2022-01-27 19:08 ` kernel test robot
2022-01-27 19:08 ` kernel test robot
2022-01-27 19:08 ` kernel test robot
2022-01-27 20:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] " Patchwork
2022-01-28 5:01 ` kernel test robot [this message]
2022-01-28 5:01 ` [RFC PATCH] i915/gvt: intel_gvt_match_device() can be static kernel test robot
2022-01-28 5:01 ` [Intel-gfx] " kernel test robot
2022-01-28 5:01 ` kernel test robot
2022-01-28 5:11 ` [Intel-gfx] [PATCH 1/3] i915/gvt: Introduce the mmio_table.c to support VFIO new mdev API kernel test robot
2022-01-28 5:11 ` kernel test robot
2022-01-28 5:11 ` kernel test robot
2022-01-31 6:34 ` Christoph Hellwig
2022-01-31 6:34 ` Christoph Hellwig
2022-02-07 7:32 ` [Intel-gfx] " Christoph Hellwig
2022-02-07 7:32 ` Christoph Hellwig
2022-02-07 8:28 ` [Intel-gfx] " Wang, Zhi A
2022-02-07 8:28 ` Wang, Zhi A
2022-02-07 8:28 ` Wang, Zhi A
2022-02-07 8:35 ` [Intel-gfx] " Christoph Hellwig
2022-02-07 8:35 ` Christoph Hellwig
2022-02-07 10:48 ` Jani Nikula
2022-02-07 10:48 ` Jani Nikula
2022-02-07 10:48 ` [Intel-gfx] " Jani Nikula
2022-02-07 11:57 ` Zhi Wang
2022-02-07 11:57 ` Zhi Wang
2022-02-07 11:57 ` [Intel-gfx] " Zhi Wang
2022-02-07 12:06 ` Christoph Hellwig
2022-02-07 12:06 ` Christoph Hellwig
2022-02-07 12:13 ` Jani Nikula
2022-02-07 12:13 ` Jani Nikula
2022-02-07 12:13 ` [Intel-gfx] " Jani Nikula
2022-02-08 8:04 ` Joonas Lahtinen
2022-02-08 8:04 ` [Intel-gfx] " Joonas Lahtinen
2022-02-08 8:04 ` Joonas Lahtinen
2022-02-07 14:47 ` [Intel-gfx] " kernel test robot
2022-02-07 14:47 ` kernel test robot
2022-02-07 14:47 ` kernel test robot
2022-02-08 14:38 ` kernel test robot
2022-02-08 14:38 ` kernel test robot
2022-02-08 14:38 ` kernel test robot
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=20220128050111.GA69282@e2c1dfe2c692 \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrence.xu@intel.com \
--cc=zhi.wang.linux@gmail.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 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.