Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [integrity:next-integrity-testing 5/5] security/integrity/ima/ima_asymmetric_keys.c:53:6: error: redefinition of 'ima_init_key_queue'
Date: Sun, 5 Jan 2020 19:58:34 -0800	[thread overview]
Message-ID: <dd99db8f-08de-d7ac-3d63-0717fc6c7ba5@linux.microsoft.com> (raw)
In-Reply-To: <1578251768.3310.49.camel@HansenPartnership.com>

On 1/5/20 11:16 AM, James Bottomley wrote:

> Well, yes, you just need to condition the build of ima_asymmetric_keys
> on a boolean instead of a tristate, so you introduce an intermediate
> one:
> 
> config IMA_ASYMMETRIC_KEYS
> 	bool
> 	default y
> 	depends on ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
> 
> James

Thanks for your help James.

Hi Mimi,

I have defined a new config as James has suggested above and verified 
the kernel builds fine with the ".config" files given by
"kbuild test robot <lkp@intel.com>".

Would it be possible to share all the ".config" files that
"kbuild test robot" would build with? I'll make sure my changes build 
fine with all those.

thanks,
  -lakshmi

  reply	other threads:[~2020-01-06  3:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  9:00 [integrity:next-integrity-testing 5/5] security/integrity/ima/ima_asymmetric_keys.c:53:6: error: redefinition of 'ima_init_key_queue' kbuild test robot
2020-01-05 17:57 ` Lakshmi Ramasubramanian
2020-01-05 18:15   ` James Bottomley
2020-01-05 18:56     ` Lakshmi Ramasubramanian
2020-01-05 19:16       ` James Bottomley
2020-01-06  3:58         ` Lakshmi Ramasubramanian [this message]
2020-01-06 13:23           ` Mimi Zohar
2020-01-06 14:58           ` James Bottomley

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=dd99db8f-08de-d7ac-3d63-0717fc6c7ba5@linux.microsoft.com \
    --to=nramas@linux.microsoft.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@linux.ibm.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