From: Mimi Zohar <zohar@linux.ibm.com>
To: kbuild test robot <lkp@intel.com>,
Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
Cc: kbuild-all@lists.01.org, linux-integrity@vger.kernel.org
Subject: Re: [integrity:next-integrity-testing 3/5] security/integrity/ima/ima_asymmetric_keys.c:70:6: sparse: sparse: symbol 'ima_queue_key' was not declared. Should it be static?
Date: Thu, 26 Dec 2019 09:27:44 -0500 [thread overview]
Message-ID: <1577370464.4487.10.camel@linux.ibm.com> (raw)
In-Reply-To: <201912251234.hUAOr3cc%lkp@intel.com>
On Wed, 2019-12-25 at 12:54 +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity-testing
> head: 11b771ffff8fc0bfc176b829d986896a7d97a44c
> commit: 466a4c055a9b9efc8704591bbfa9041c77f66c46 [3/5] IMA: Define workqueue for early boot "key" measurements
> reproduce:
> # apt-get install sparse
> # sparse version: v0.6.1-129-g341daf20-dirty
> git checkout 466a4c055a9b9efc8704591bbfa9041c77f66c46
> 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 >>)
>
> >> security/integrity/ima/ima_asymmetric_keys.c:70:6: sparse: sparse: symbol 'ima_queue_key' was not declared. Should it be static?
>
> Please review and possibly fold the followup patch.
Thank you for following next-integrity-testing branch and providing a fix.
Mimi
prev parent reply other threads:[~2019-12-26 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 4:54 [integrity:next-integrity-testing 3/5] security/integrity/ima/ima_asymmetric_keys.c:70:6: sparse: sparse: symbol 'ima_queue_key' was not declared. Should it be static? kbuild test robot
2019-12-25 4:54 ` [RFC PATCH integrity] IMA: ima_queue_key() can be static kbuild test robot
2019-12-25 6:43 ` Lakshmi Ramasubramanian
2019-12-26 14:27 ` Mimi Zohar
2019-12-26 18:33 ` Lakshmi Ramasubramanian
2019-12-26 14:27 ` Mimi Zohar [this message]
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=1577370464.4487.10.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-integrity@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nramas@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).