From: Eric Dumazet <eric.dumazet@gmail.com>
To: balbi@ti.com
Cc: Piotr Hosowicz <piotr@hosowicz.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: error in 2.6.37-git10
Date: Fri, 14 Jan 2011 12:34:41 +0100 [thread overview]
Message-ID: <1295004881.3937.9.camel@edumazet-laptop> (raw)
In-Reply-To: <20110114105639.GL2476@legolas.emea.dhcp.ti.com>
Le vendredi 14 janvier 2011 à 12:56 +0200, Felipe Balbi a écrit :
> Hi,
>
> On Fri, Jan 14, 2011 at 11:53:02AM +0100, Piotr Hosowicz wrote:
> > >I corrected and am building again. Hope this helps.
> >
> > I don't know why but it failed again. I disabled and am building again.
>
> for me it builds ok:
>
> CC [M] fs/ecryptfs/dentry.o
> CC [M] fs/ecryptfs/file.o
> CC [M] fs/ecryptfs/inode.o
> CC [M] fs/ecryptfs/main.o
> CC [M] fs/ecryptfs/super.o
> CC [M] fs/ecryptfs/mmap.o
> CC [M] fs/ecryptfs/read_write.o
> CC [M] fs/ecryptfs/crypto.o
> CC [M] fs/ecryptfs/keystore.o
> CC [M] fs/ecryptfs/messaging.o
> CC [M] fs/ecryptfs/miscdev.o
> CC [M] fs/ecryptfs/kthread.o
> CC [M] fs/ecryptfs/debug.o
> LD [M] fs/ecryptfs/ecryptfs.o
>
> weird.
>
This is because it was fixed meanwhile
commit 6254b32b5791e47ba1c679d023f26985fa34755a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Jan 13 17:19:38 2011 -0800
ecryptfs: fix broken build
Stephen Rothwell reports that the vfs merge broke the build of ecryptfs.
The breakage comes from commit 66cb76666d69 ("sanitize ecryptfs
->mount()") which was obviously not even build tested. Tssk, tssk, Al.
This is the minimal build fixup for the situation, although I don't have
a filesystem to actually test it with.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
prev parent reply other threads:[~2011-01-14 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 9:51 Piotr Hosowicz
2011-01-14 9:57 ` Felipe Balbi
2011-01-14 10:07 ` Piotr Hosowicz
2011-01-14 10:08 ` Felipe Balbi
2011-01-14 10:13 ` Piotr Hosowicz
2011-01-14 10:53 ` Piotr Hosowicz
2011-01-14 10:56 ` Felipe Balbi
2011-01-14 11:34 ` Eric Dumazet [this message]
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=1295004881.3937.9.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@hosowicz.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
all inboxes | Powered by JetHome®