All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH kunit-next 1/2] kunit: generalize kunit_resource API beyond allocated resources
Date: Wed, 04 Mar 2020 11:10:34 +0800	[thread overview]
Message-ID: <202003041126.LVDjTFup%lkp@intel.com> (raw)
In-Reply-To: <1583251361-12748-2-git-send-email-alan.maguire@oracle.com>

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

Hi Alan,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[also build test WARNING on v5.6-rc4 next-20200303]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Alan-Maguire/kunit-extend-kunit-resources-API/20200304-042258
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 98d54f81e36ba3bf92172791eba5ca5bd813989b
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-174-g094d5a94-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

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


sparse warnings: (new ones prefixed by >>)

>> lib/kunit/test.c:328:6: sparse: sparse: symbol 'kunit_release_resource' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2020-03-04  3:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 16:02 [RFC PATCH kunit-next 0/2] kunit: extend kunit resources API Alan Maguire
2020-03-03 16:02 ` [RFC PATCH kunit-next 1/2] kunit: generalize kunit_resource API beyond allocated resources Alan Maguire
2020-03-04  3:10   ` kbuild test robot [this message]
2020-03-04  3:11   ` [RFC PATCH] kunit: kunit_release_resource() can be static kbuild test robot
2020-03-12  0:14   ` [RFC PATCH kunit-next 1/2] kunit: generalize kunit_resource API beyond allocated resources Brendan Higgins
2020-03-03 16:02 ` [RFC PATCH kunit-next 2/2] kunit: add support for named resources Alan Maguire
2020-03-13  0:09   ` Brendan Higgins

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=202003041126.LVDjTFup%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.