public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Avinash Kondareddy <akndr41@gmail.com>
Cc: kbuild-all@01.org, linux-kbuild@vger.kernel.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Brendan Higgins <brendanhiggins@google.com>
Subject: [kbuild:kunit 11/17] kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls through to next function fake_resource_init()
Date: Fri, 10 May 2019 22:57:20 +0800	[thread overview]
Message-ID: <201905102217.SH2wp6bv%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kunit
head:   c505c0b2e6237c729634327c178f5b0094f1c958
commit: 3ad04f25d34ca374d43673bb84ddad4196857320 [11/17] kunit: test: add test managed resource tests
config: x86_64-randconfig-s4-05101924 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout 3ad04f25d34ca374d43673bb84ddad4196857320
        # save the attached .config to linux build tree
        make ARCH=x86_64 

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

All warnings (new ones prefixed by >>):

>> kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls through to next function fake_resource_init()

---
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: 36591 bytes --]

                 reply	other threads:[~2019-05-10 14:58 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=201905102217.SH2wp6bv%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akndr41@gmail.com \
    --cc=brendanhiggins@google.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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