All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: [tip:sched/core 44/47] kernel/exit.o: warning: objtool: do_exit() falls through to next function complete_and_exit()
Date: Fri, 23 Sep 2016 02:37:11 +0800	[thread overview]
Message-ID: <201609230208.d3pdLI2R%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head:   a18a579e5f84daa74f64b1f1b652b4a6a8d6f8b4
commit: 9af6528ee9b682df7f29dbee86fbba0b67eab944 [44/47] sched/core: Optimize __schedule()
config: x86_64-randconfig-v0-09221826 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        git checkout 9af6528ee9b682df7f29dbee86fbba0b67eab944
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> kernel/exit.o: warning: objtool: do_exit() falls through to next function complete_and_exit()

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26246 bytes --]

             reply	other threads:[~2016-09-22 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 18:37 kbuild test robot [this message]
2016-09-22 21:21 ` [PATCH] objtool: add do_task_dead() to global noreturn list Josh Poimboeuf
2016-09-23  5:33   ` [tip:sched/core] objtool: Add " tip-bot for Josh Poimboeuf

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=201609230208.d3pdLI2R%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 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.