From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the security-testing tree
Date: Tue, 09 Aug 2011 21:48:29 -0400 [thread overview]
Message-ID: <1312940909.2611.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20110810105840.cb0b3ac63c84b51b98029d8c@canb.auug.org.au>
On Wed, 2011-08-10 at 10:58 +1000, Stephen Rothwell wrote:
> Hi James,
>
> After merging the security-testing tree, today's linux-next build
> (powerpc ppc64_defconfig) failed like this:
>
> fs/reiserfs/xattr_security.c: In function 'reiserfs_security_init':
> fs/reiserfs/xattr_security.c:69:2: error: implicit declaration of function 'security_old_inode_init_security'
>
> Caused by commit 9d8f13ba3f48 ("security: new
> security_inode_init_security API adds function callback"). Forgotten
> include?
>
> I have used the security-testing tree from next-20110809 for today.
No, I left out the stub definition in the include. James, how do you
want me to correct this and the missing 'inline'? Should I be updating
the original patches or submitting them as new patches?
thanks,
Mimi
next prev parent reply other threads:[~2011-08-10 1:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 0:58 linux-next: build failure after merge of the security-testing tree Stephen Rothwell
2011-08-10 1:48 ` Mimi Zohar [this message]
2011-08-10 7:21 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2011-08-12 2:47 Stephen Rothwell
2011-08-15 4:04 ` Stephen Rothwell
2011-06-29 3:48 Stephen Rothwell
2011-06-29 4:16 ` Tetsuo Handa
2011-06-29 7:36 ` James Morris
2010-10-19 3:57 Stephen Rothwell
2010-10-19 4:09 ` Eric Paris
2010-08-02 2:16 Stephen Rothwell
2010-08-03 0:04 ` John Johansen
2010-08-05 1:37 ` Stephen Rothwell
2010-07-30 2:06 Stephen Rothwell
2010-07-30 3:54 ` James Morris
2010-07-30 6:01 ` Stephen Rothwell
2010-07-30 7:31 ` John Johansen
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=1312940909.2611.10.camel@localhost.localdomain \
--to=zohar@linux.vnet.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.