mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: [tip:WIP.x86/alternatives 2/9] kernel/jump_label.c:387:10-11: WARNING: return of 0/1 in function 'jump_label_can_update_check' with return type bool
Date: Sat, 20 Apr 2019 08:25:46 +0800	[thread overview]
Message-ID: <201904200838.Ti8u2zuO%lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/alternatives
head:   1f30946b1a01baf22df6faf74c0a1e602bb6cac7
commit: 41bef31d0abe29b5888b33b526cacc8a30795318 [2/9] jump_label: Add the jump_label_can_update_check() helper

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>



coccinelle warnings: (new ones prefixed by >>)

>> kernel/jump_label.c:387:10-11: WARNING: return of 0/1 in function 'jump_label_can_update_check' with return type bool

vim +/jump_label_can_update_check +387 kernel/jump_label.c

   376	
   377	bool jump_label_can_update_check(struct jump_entry *entry, bool init)
   378	{
   379		/*
   380		 * An entry->code of 0 indicates an entry which has been
   381		 * disabled because it was in an init text area.
   382		 */
   383		if (init || !jump_entry_is_init(entry)) {
   384			if (!kernel_text_address(jump_entry_code(entry))) {
   385				WARN_ONCE(1, "can't patch jump_label at %pS",
   386					  (void *)jump_entry_code(entry));
 > 387				return 0;
   388			}
   389			return 1;
   390		}
   391		return 0;
   392	}
   393	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

                 reply	other threads:[~2019-04-20  0:26 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=201904200838.Ti8u2zuO%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bristot@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tipbuild@zytor.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 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®