mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rong Tao <rtoax@foxmail.com>
To: mcgrof@kernel.org
Cc: ast@kernel.org, frederic@kernel.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, mbenes@suse.cz,
	mhiramat@kernel.org, pmladek@suse.com, prasad@linux.vnet.ibm.com,
	qperret@google.com, rongtao@cestc.cn, rtoax@foxmail.com,
	tglx@linutronix.de, will@kernel.org
Subject: Re: [PATCH] samples/hw_breakpoint: Fix kernel BUG 'invalid opcode: 0000'
Date: Tue, 25 Jul 2023 21:38:48 +0800	[thread overview]
Message-ID: <tencent_B02B6BED124665ED9563140A71C1004D0805@qq.com> (raw)
In-Reply-To: <ZL7OJQBXBz1a3Sk3@bombadil.infradead.org>

Hi Luis

The 'kernel test robot' report an error [0]:

	>> samples/hw_breakpoint/data_breakpoint.c:73:2: error: call to undeclared function '__symbol_put'; 
	ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration]
	           __symbol_put(ksym_name);
	           ^
	   samples/hw_breakpoint/data_breakpoint.c:73:2: note: did you mean '__symbol_get'?
	   include/linux/module.h:301:7: note: '__symbol_get' declared here
	   void *__symbol_get(const char *symbol);
	         ^
	   1 error generated.

Do I need to do something? It seems that no changes need to be made from the
mainline code.

[0] https://lore.kernel.org/oe-kbuild-all/202307250926.06DQZjVe-lkp@intel.com/

Rong


  reply	other threads:[~2023-07-25 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 10:47 Rong Tao
2023-07-24 12:59 ` Petr Mladek
2023-07-24 19:16   ` Luis Chamberlain
2023-07-25 13:38     ` Rong Tao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-16 15:05 Rong Tao
2023-04-17  9:38 ` Petr Mladek

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=tencent_B02B6BED124665ED9563140A71C1004D0805@qq.com \
    --to=rtoax@foxmail.com \
    --cc=ast@kernel.org \
    --cc=frederic@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=pmladek@suse.com \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=qperret@google.com \
    --cc=rongtao@cestc.cn \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®