From: kernel test robot <lkp@intel.com>
To: Sean Paul <sean@poorly.run>, dri-devel@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>, David Airlie <airlied@linux.ie>,
daniel.vetter@ffwll.ch, Chris Wilson <chris@chris-wilson.co.uk>,
Sean Paul <seanpaul@chromium.org>,
tzimmermann@suse.de, Steven Rostedt <rostedt@goodmis.org>
Subject: [RFC PATCH] drm/print: trace_arr can be static
Date: Tue, 9 Jun 2020 09:45:05 +0800 [thread overview]
Message-ID: <20200609014505.GA50763@37d9db08ab2a> (raw)
In-Reply-To: <20200608210505.48519-14-sean@poorly.run>
Signed-off-by: kernel test robot <lkp@intel.com>
---
drm_print.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_print.c b/drivers/gpu/drm/drm_print.c
index c4bef38921db1..a50d0b24c911f 100644
--- a/drivers/gpu/drm/drm_print.c
+++ b/drivers/gpu/drm/drm_print.c
@@ -69,7 +69,7 @@ MODULE_PARM_DESC(trace, DEBUG_PARM_DESC("tracefs"));
module_param_named(trace, __drm_debug_trace, int, 0600);
#ifdef CONFIG_TRACING
-struct trace_array *trace_arr;
+static struct trace_array *trace_arr;
#endif
void __drm_puts_coredump(struct drm_printer *p, const char *str)
next prev parent reply other threads:[~2020-06-09 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200608210505.48519-1-sean@poorly.run>
2020-06-08 21:05 ` [PATCH v5 13/13] drm/print: Add tracefs support to the drm logging helpers Sean Paul
2020-06-08 23:47 ` kernel test robot
2020-06-09 1:45 ` kernel test robot
2020-06-09 15:49 ` [PATCH v6 " Sean Paul
2020-06-10 15:01 ` Steven Rostedt
2020-06-10 15:29 ` Sean Paul
2020-06-09 1:45 ` kernel test robot [this message]
2020-06-10 7:57 ` [PATCH v5 " Pekka Paalanen
2020-06-10 13:29 ` Sean Paul
2020-06-10 14:09 ` Pekka Paalanen
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=20200609014505.GA50763@37d9db08ab2a \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).