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 2/2] tee: add AMD-TEE driver
Date: Sat, 26 Oct 2019 05:02:51 +0800	[thread overview]
Message-ID: <201910260459.II3OXn8v%lkp@intel.com> (raw)
In-Reply-To: <fd7b187b01cccd690dc3c71d6c5f2520bb9e303a.1571818136.git.Rijo-john.Thomas@amd.com>

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

Hi Rijo-john",

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc4 next-20191025]
[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/Thomas-Rijo-john/TEE-driver-for-AMD-APUs/20191025-081700
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 39a38bcba4ab6e5285b07675b0e42c96eec35e67
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-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 >>)

>> drivers/tee/amdtee/core.c:22:27: sparse: sparse: symbol 'shmctx' was not declared. Should it be static?

Please review and possibly fold the followup patch.

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

  parent reply	other threads:[~2019-10-25 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 11:30 [RFC PATCH 0/2] TEE driver for AMD APUs Thomas, Rijo-john
2019-10-23 11:30 ` [RFC PATCH 1/2] tee: allow compilation of tee subsystem for AMD CPUs Thomas, Rijo-john
2019-10-23 11:31 ` [RFC PATCH 2/2] tee: add AMD-TEE driver Thomas, Rijo-john
2019-10-25  8:13   ` kbuild test robot
2019-10-25 21:02   ` [RFC PATCH] tee: shmctx can be static kbuild test robot
2019-10-25 21:02   ` kbuild test robot [this message]
2019-11-05 15:28   ` [RFC PATCH 2/2] tee: add AMD-TEE driver Jens Wiklander
2019-11-26 13:01     ` Thomas, Rijo-john
2019-11-05 15:17 ` [RFC PATCH 0/2] TEE driver for AMD APUs Jens Wiklander
2019-11-26 13:00   ` Thomas, Rijo-john

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=201910260459.II3OXn8v%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.