Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Xiong Zhang <xiong.y.zhang@intel.com>, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, kbuild-all@lists.01.org, chris@chris-wilson.co.uk
Subject: [Intel-gfx] [RFC PATCH] drm/i915: intel_detect_pch_virt() can be static
Date: Mon, 14 Dec 2020 18:10:25 +0800	[thread overview]
Message-ID: <20201214101025.GA50122@45a86e22e0de> (raw)
In-Reply-To: <20201214070113.16177-1-xiong.y.zhang@intel.com>


Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 intel_pch.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/intel_pch.c b/drivers/gpu/drm/i915/intel_pch.c
index ca5989700ecf23..a3f84327535688 100644
--- a/drivers/gpu/drm/i915/intel_pch.c
+++ b/drivers/gpu/drm/i915/intel_pch.c
@@ -184,7 +184,7 @@ intel_virt_detect_pch(const struct drm_i915_private *dev_priv)
 	return id;
 }
 
-void intel_detect_pch_virt(struct drm_i915_private *dev_priv)
+static void intel_detect_pch_virt(struct drm_i915_private *dev_priv)
 {
 	unsigned short id;
 	enum intel_pch pch_type;
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-12-14 10:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  7:01 [Intel-gfx] [PATCH] drm/i915: Try to guess PCH type even without ISA bridge Xiong Zhang
2020-12-14  7:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-12-14  7:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-12-18  9:05   ` [Intel-gfx] [PATCH v2] " Xiong Zhang
2020-12-22  5:15     ` Zhenyu Wang
2020-12-23  8:39       ` Zhang, Xiong Y
2020-12-23  8:59     ` Jani Nikula
2020-12-24  2:42       ` Zhang, Xiong Y
2020-12-24  2:54       ` Zhang, Xiong Y
2020-12-24  4:49         ` Zhenyu Wang
2021-01-13  4:53       ` [Intel-gfx] [PATCH v3] " Xiong Zhang
2021-01-14  0:58       ` [Intel-gfx] [PATCH v4] " Xiong Zhang
2021-01-14  5:14         ` Zhenyu Wang
2021-01-15 10:50           ` Jani Nikula
2021-01-15 11:01             ` Joonas Lahtinen
2021-01-18  6:04               ` Zhenyu Wang
2021-01-18  9:56                 ` Jani Nikula
2020-12-18 10:16   ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge (rev2) Patchwork
2020-12-18 11:27   ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-01-13  5:23   ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Try to guess PCH type even without ISA bridge (rev3) Patchwork
2021-01-13  5:52   ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-01-14  2:01   ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge (rev4) Patchwork
2021-01-14  4:59   ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-14  7:22 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Try to guess PCH type even without ISA bridge Patchwork
2020-12-14  7:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-12-14  9:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-14 10:10 ` [Intel-gfx] [PATCH] " kernel test robot
2020-12-14 10:10 ` kernel test robot [this message]
2020-12-14 12:50 ` 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=20201214101025.GA50122@45a86e22e0de \
    --to=lkp@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=xiong.y.zhang@intel.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