All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mark:stacktrace/tests 29/30] lib/stacktrace_kunit.c:52:20: error: implicit declaration of function 'stack_trace_save'; did you mean 'stack_tracer_enable'?
Date: Thu, 6 Jun 2024 01:10:19 +0800	[thread overview]
Message-ID: <202406060130.PMIOyVL2-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git stacktrace/tests
head:   b355c7c11a4a1cec3478bc7a2f129638d9b5116d
commit: bd60ed306ab25ea1c027a362c756729923d62548 [29/30] WIP: lib: add basic stacktrace tests
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240606/202406060130.PMIOyVL2-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240606/202406060130.PMIOyVL2-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202406060130.PMIOyVL2-lkp@intel.com/

All errors (new ones prefixed by >>):

   lib/stacktrace_kunit.c: In function 'std_save_stacktrace':
>> lib/stacktrace_kunit.c:52:20: error: implicit declaration of function 'stack_trace_save'; did you mean 'stack_tracer_enable'? [-Werror=implicit-function-declaration]
      52 |         std->len = stack_trace_save(std->stack_trace,
         |                    ^~~~~~~~~~~~~~~~
         |                    stack_tracer_enable
   cc1: some warnings being treated as errors


vim +52 lib/stacktrace_kunit.c

    49	
    50	static void std_save_stacktrace(struct stacktrace_test_data *std)
    51	{
  > 52		std->len = stack_trace_save(std->stack_trace,
    53					    NR_STACKTRACE_ELEMS,
    54					    0);
    55		std->hit = true;
    56	}
    57	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-06-05 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202406060130.PMIOyVL2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.