public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mimi Zohar <zohar@us.ibm.com>
Subject: Re: linux-next: Tree for Feb 19 (security/integrity/ima)
Date: Wed, 20 Feb 2013 11:50:50 -0500	[thread overview]
Message-ID: <1361379050.29360.12.camel@falcor1> (raw)
In-Reply-To: <512418A5.9010006@infradead.org>

On Tue, 2013-02-19 at 16:28 -0800, Randy Dunlap wrote:
> On 02/18/13 22:03, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20130218:
> > 
> 
> on x86_64:
> 
>   CC      security/integrity/ima/ima_policy.o
> security/integrity/ima/ima_policy.c: In function 'ima_parse_rule':
> security/integrity/ima/ima_policy.c:538:4: error: implicit declaration of function 'part_pack_uuid' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> make[4]: *** [security/integrity/ima/ima_policy.o] Error 1
> 
> 
> Full randconfig file is attached.

part_pack_uuid() is only defined for CONFIG_BLOCK in
include/linux/genhd.h.  One solution would be to add a stub function
definition in include/linux/genhd.h, the other option would be to ifndef
CONFIG_BLOCK in C code.

thanks,

Mimi





  reply	other threads:[~2013-02-20 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  6:03 linux-next: Tree for Feb 19 Stephen Rothwell
2013-02-20  0:28 ` linux-next: Tree for Feb 19 (security/integrity/ima) Randy Dunlap
2013-02-20 16:50   ` Mimi Zohar [this message]
2013-02-20 19:30     ` [PATCH -next] security/integrity/ima: make part_pack_uuid() always visible Randy Dunlap
2013-02-20 19:46       ` Mimi Zohar

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=1361379050.29360.12.camel@falcor1 \
    --to=zohar@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zohar@us.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