From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Mimi Zohar <zohar@linux•vnet.ibm.com>,
Eric Paris <eparis@redhat•com>
Subject: linux-next: vfs tree build failure
Date: Thu, 28 Jan 2010 12:00:00 +1100 [thread overview]
Message-ID: <20100128120000.cd804756.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Hi Al,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
fs/namei.c: In function 'do_filp_open':
fs/namei.c:1740: error: too many arguments to function 'ima_file_check'
fs/namei.c:1800: error: too many arguments to function 'ima_file_check'
Caused by commit dbcbe631a87d21e429f156edee4ffdeb7dbd84ce ("ima: rename
ima_path_check to ima_file_check").
I have used the vfs tree from next-20100125 again today.
P.S. that commit has author Mimi Zohar <zohar@linux•vnet.ibm.com>, but is
signed off by only Eric Paris <eparis@redhat•com> and Al Viro
<viro@zeniv•linux.org.uk> (and merely acked by Zohar
<zohar@linux•vnet.ibm.com>).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-01-28 1:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 1:00 Stephen Rothwell [this message]
2010-01-28 1:54 ` linux-next: vfs tree build failure Al Viro
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 0:37 Stephen Rothwell
2009-05-07 3:53 Stephen Rothwell
2009-05-07 4:04 ` Al Viro
2009-04-02 2:12 Stephen Rothwell
2009-04-03 4:43 ` Stephen Rothwell
2009-04-02 1:52 Stephen Rothwell
2009-04-03 4:44 ` Stephen Rothwell
2008-10-20 6:18 Stephen Rothwell
2008-10-20 7:13 ` Dave Chinner
2008-10-20 7:40 ` Christoph Hellwig
2008-10-15 6:49 Stephen Rothwell
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=20100128120000.cd804756.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=eparis@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@ZenIV$(echo .)linux.org.uk \
--cc=zohar@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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