All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: kbuild-all@lists.01.org
Subject: [Intel-gfx] [RFC PATCH] drm/i915/perf: i915_perf_mmap() can be static
Date: Sat, 18 Jul 2020 19:44:28 +0800	[thread overview]
Message-ID: <20200718114427.GA32671@c5c18c185bfe> (raw)
In-Reply-To: <20200718000437.69033-5-umesh.nerlige.ramappa@intel.com>


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

diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index e77582761a642..90535e38b91b9 100644
--- a/drivers/gpu/drm/i915/i915_perf.c
+++ b/drivers/gpu/drm/i915/i915_perf.c
@@ -3423,7 +3423,7 @@ static const struct vm_operations_struct vm_ops_oa = {
 	.fault = vm_fault_oa,
 };
 
-int i915_perf_mmap(struct file *file, struct vm_area_struct *vma)
+static int i915_perf_mmap(struct file *file, struct vm_area_struct *vma)
 {
 	struct i915_perf_stream *stream = file->private_data;
 	int len;
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] drm/i915/perf: i915_perf_mmap() can be static
Date: Sat, 18 Jul 2020 19:44:28 +0800	[thread overview]
Message-ID: <20200718114427.GA32671@c5c18c185bfe> (raw)
In-Reply-To: <20200718000437.69033-5-umesh.nerlige.ramappa@intel.com>

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]


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

diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index e77582761a642..90535e38b91b9 100644
--- a/drivers/gpu/drm/i915/i915_perf.c
+++ b/drivers/gpu/drm/i915/i915_perf.c
@@ -3423,7 +3423,7 @@ static const struct vm_operations_struct vm_ops_oa = {
 	.fault = vm_fault_oa,
 };
 
-int i915_perf_mmap(struct file *file, struct vm_area_struct *vma)
+static int i915_perf_mmap(struct file *file, struct vm_area_struct *vma)
 {
 	struct i915_perf_stream *stream = file->private_data;
 	int len;

  parent reply	other threads:[~2020-07-18 11:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18  0:04 [Intel-gfx] [PATCH 0/4] Allow privileged user to map the OA buffer Umesh Nerlige Ramappa
2020-07-18  0:04 ` [Intel-gfx] [PATCH 1/4] drm/i915/perf: Ensure observation logic is not clock gated Umesh Nerlige Ramappa
2020-07-18 19:09   ` Lionel Landwerlin
2020-07-18  0:04 ` [Intel-gfx] [PATCH 2/4] drm/i915/perf: Whitelist OA report trigger registers Umesh Nerlige Ramappa
2020-07-18 19:11   ` Lionel Landwerlin
2020-07-18  0:04 ` [Intel-gfx] [PATCH 3/4] drm/i915/perf: Whitelist OA counter and buffer registers Umesh Nerlige Ramappa
2020-07-18  0:04 ` [Intel-gfx] [PATCH 4/4] drm/i915/perf: Map OA buffer to user space for gen12 performance query Umesh Nerlige Ramappa
2020-07-18 11:44   ` kernel test robot
2020-07-18 11:44     ` kernel test robot
2020-07-18 11:44   ` kernel test robot [this message]
2020-07-18 11:44     ` [RFC PATCH] drm/i915/perf: i915_perf_mmap() can be static kernel test robot
2020-07-20 12:21   ` [Intel-gfx] [PATCH 4/4] drm/i915/perf: Map OA buffer to user space for gen12 performance query Chris Wilson
2020-07-18  0:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Allow privileged user to map the OA buffer (rev2) Patchwork
2020-07-18  0:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-07-18  0:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork

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=20200718114427.GA32671@c5c18c185bfe \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=umesh.nerlige.ramappa@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 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.