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: [PATCH v5 1/4] KEYS: trusted: Add generic trusted keys framework
Date: Wed, 03 Jun 2020 04:54:52 +0800	[thread overview]
Message-ID: <202006030421.O34mEEea%lkp@intel.com> (raw)
In-Reply-To: <1591107505-6030-2-git-send-email-sumit.garg@linaro.org>

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

Hi Sumit,

I love your patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.7 next-20200602]
[cannot apply to security/next-testing dhowells-fs/fscache-next]
[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/Sumit-Garg/Introduce-TEE-based-Trusted-Keys-support/20200602-222340
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git f359287765c04711ff54fbd11645271d8e5ff763
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2388a096e7865c043e83ece4e26654bd3d1a20d5)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 

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

All warnings (new ones prefixed by >>, old ones prefixed by <<):

>> security/keys/trusted-keys/trusted_tpm1.c:945:5: warning: no previous prototype for function 'tpm_trusted_get_random' [-Wmissing-prototypes]
int tpm_trusted_get_random(unsigned char *key, size_t key_len)
^
security/keys/trusted-keys/trusted_tpm1.c:945:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int tpm_trusted_get_random(unsigned char *key, size_t key_len)
^
static
1 warning generated.

vim +/tpm_trusted_get_random +945 security/keys/trusted-keys/trusted_tpm1.c

   944	
 > 945	int tpm_trusted_get_random(unsigned char *key, size_t key_len)
   946	{
   947		return tpm_get_random(chip, key, key_len);
   948	}
   949	

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

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

  parent reply	other threads:[~2020-06-02 20:54 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 14:18 [PATCH v5 0/4] Introduce TEE based Trusted Keys support Sumit Garg
2020-06-02 14:30 ` Sumit Garg
2020-06-02 14:18 ` Sumit Garg
2020-06-02 14:18 ` [op-tee] " Sumit Garg
2020-06-02 14:18 ` [PATCH v5 1/4] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2020-06-02 14:30   ` Sumit Garg
2020-06-02 14:18   ` Sumit Garg
2020-06-02 14:18   ` [op-tee] " Sumit Garg
2020-06-02 19:33   ` kbuild test robot
2020-06-02 20:54   ` kbuild test robot [this message]
2020-06-02 22:37   ` kbuild test robot
2020-06-15 18:24   ` Jarkko Sakkinen
2020-06-15 18:24     ` Jarkko Sakkinen
2020-06-15 18:24     ` [op-tee] " Jarkko Sakkinen
2020-06-15 18:24     ` Jarkko Sakkinen
2020-06-16 13:32     ` Sumit Garg
2020-06-16 13:44       ` Sumit Garg
2020-06-16 13:32       ` Sumit Garg
2020-06-16 13:32       ` Sumit Garg
2020-06-17 23:14       ` Jarkko Sakkinen
2020-06-17 23:14         ` Jarkko Sakkinen
2020-06-17 23:14         ` Jarkko Sakkinen
2020-06-17 23:14         ` Jarkko Sakkinen
2020-06-18  6:42         ` Sumit Garg
2020-06-18  6:54           ` Sumit Garg
2020-06-18  6:42           ` Sumit Garg
2020-06-18  6:42           ` Sumit Garg
2020-06-18  7:19           ` Jarkko Sakkinen
2020-06-18  7:19             ` Jarkko Sakkinen
2020-06-18  7:19             ` Jarkko Sakkinen
2020-06-18  7:19             ` Jarkko Sakkinen
2020-06-02 14:18 ` [PATCH v5 2/4] KEYS: trusted: Introduce TEE based Trusted Keys Sumit Garg
2020-06-02 14:30   ` Sumit Garg
2020-06-02 14:18   ` Sumit Garg
2020-06-02 14:18   ` [op-tee] " Sumit Garg
2020-06-02 14:18 ` [PATCH v5 3/4] doc: trusted-encrypted: updates with TEE as a new trust source Sumit Garg
2020-06-02 14:30   ` Sumit Garg
2020-06-02 14:18   ` Sumit Garg
2020-06-02 14:18   ` [op-tee] " Sumit Garg
2020-06-02 14:18 ` [PATCH v5 4/4] MAINTAINERS: Add entry for TEE based Trusted Keys Sumit Garg
2020-06-02 14:30   ` Sumit Garg
2020-06-02 14:18   ` Sumit Garg
2020-06-02 14:18   ` [op-tee] " Sumit Garg
2020-06-02 14:43 ` [PATCH v5 0/4] Introduce TEE based Trusted Keys support James Bottomley
2020-06-02 14:43   ` James Bottomley
2020-06-02 14:43   ` [op-tee] " James Bottomley
2020-06-02 14:43   ` James Bottomley
2020-06-03  8:07   ` Sumit Garg
2020-06-03  8:19     ` Sumit Garg
2020-06-03  8:07     ` Sumit Garg
2020-06-03  8:07     ` [op-tee] " Sumit Garg
     [not found] < <CAFA6WYOoMdLJ2g3gocZBZWdu-7Nfw7LKHnzX8S8FKeC7cuNwYg@mail.gmail.com>
2020-06-03  8:50 ` Luke Hinds
2020-06-03 11:45   ` Sumit Garg
2020-06-03 11:57     ` Sumit Garg
2020-06-03 11:45     ` Sumit Garg
2020-06-03 11:45     ` [op-tee] " Sumit Garg

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=202006030421.O34mEEea%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.