From: Mike Frysinger <vapier.adi@gmail.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
James Morris <jmorris@namei.org>,
David Safford <safford@watson.ibm.com>,
Serge Hallyn <serue@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH] integrity: shmem zero fix
Date: Tue, 10 Feb 2009 23:05:26 -0500 [thread overview]
Message-ID: <8bd0f97a0902102005i70c408afhedf6b1d197e2e308@mail.gmail.com> (raw)
In-Reply-To: <1234324879-12411-1-git-send-email-zohar@linux.vnet.ibm.com>
On Tue, Feb 10, 2009 at 23:01, Mimi Zohar wrote:
> Based on comments from Mike Frysinger and Randy Dunlap:
> (http://lkml.org/lkml/2009/2/9/262)
> - moved ima.h include before CONFIG_SHMEM test to fix compiler error
> on Blackfin:
> mm/shmem.c: In function 'shmem_zero_setup':
> mm/shmem.c:2670: error: implicit declaration of function 'ima_shm_check'
>
> - added 'struct linux_binprm' in ima.h to fix compiler warning on Blackfin:
> In file included from mm/shmem.c:32:
> include/linux/ima.h:25: warning: 'struct linux_binprm' declared inside
> parameter list
> include/linux/ima.h:25: warning: its scope is only this definition or
> declaration, which is probably not what you want
>
> - moved fs.h include within _LINUX_IMA_H definition
>
> Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
-mike
next prev parent reply other threads:[~2009-02-11 4:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 4:01 [PATCH] integrity: shmem zero fix Mimi Zohar
2009-02-11 4:05 ` Mike Frysinger [this message]
2009-02-11 4:30 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 2:04 Mimi Zohar
2009-02-09 23:02 Mimi Zohar
2009-02-10 0:03 ` Mike Frysinger
2009-02-10 0:10 ` Randy Dunlap
2009-02-10 22:34 ` Andrew Morton
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=8bd0f97a0902102005i70c408afhedf6b1d197e2e308@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=safford@watson.ibm.com \
--cc=serue@us.ibm.com \
--cc=zohar@linux.vnet.ibm.com \
--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 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.