All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH trace] ftrace: lookup_rec() can be static
Date: Thu, 24 Oct 2019 11:46:51 +0800	[thread overview]
Message-ID: <20191024034651.ax6nyat57x46jhhn@4978f4969bb8> (raw)
In-Reply-To: <201910241131.4IopbCWV%lkp@intel.com>

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


Fixes: 3ac423d90272 ("ftrace: Add register_ftrace_direct() for custom trampolines")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 ftrace.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 1916da21d880b..f945af27560ea 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -1544,7 +1544,7 @@ static int ftrace_cmp_recs(const void *a, const void *b)
 	return 0;
 }
 
-struct dyn_ftrace *lookup_rec(unsigned long start, unsigned long end)
+static struct dyn_ftrace *lookup_rec(unsigned long start, unsigned long end)
 {
 	struct ftrace_page *pg;
 	struct dyn_ftrace *rec = NULL;

      reply	other threads:[~2019-10-24  3:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  3:46 [trace:ftrace/direct 24/25] kernel/trace/ftrace.c:1547:19: sparse: sparse: symbol 'lookup_rec' was not declared. Should it be static? kbuild test robot
2019-10-24  3:46 ` kbuild test robot [this message]

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=20191024034651.ax6nyat57x46jhhn@4978f4969bb8 \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.