mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Francesco Allertsen <fallertsen@gmail.com>
Cc: Alex Elder <aelder@sgi.com>,
	xfs-masters@oss.sgi.com, Christoph Hellwig <hch@lst.de>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Dave Chinner <dchinner@redhat.com>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: xfs compile error with the latest -git
Date: Wed, 27 Jul 2011 08:35:59 +0200	[thread overview]
Message-ID: <20110727063559.GB1641@x4.trippels.de> (raw)
In-Reply-To: <20110726233246.GA8168@fujiko>

On 2011.07.27 at 01:32 +0200, Francesco Allertsen wrote:
> Hi all,
>  I have tried to compile the latest -git today and I got the following
> error while compiling the xfs filesystem.
> 
>   CC      fs/xfs/linux-2.6/xfs_iops.o
>   fs/xfs/linux-2.6/xfs_iops.c:1025:14: error: 'xfs_get_acl' undeclared here (not in a function)
> 
> I have bisected the problem and the first bad commit is this one
> 
>   commit 4e34e719e457f2e031297175410fc0bd4016a085
>   Author: Christoph Hellwig <hch@lst.de>
>   Date:   Sat Jul 23 17:37:31 2011 +0200
> 
>   fs: take the ACL checks to common code
> 
>   Replace the ->check_acl method with a ->get_acl method that simply reads an
>   ACL from disk after having a cache miss.  This means we can replace the ACL
>   checking boilerplate code with a single implementation in namei.c.
> 
>   Signed-off-by: Christoph Hellwig <hch@lst.de>
>   Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> 
> Could you please solve this problem?  I have attached also the .config
> file if you need it.

It's already solved:  http://lkml.org/lkml/2011/7/26/94
But somehow Linus didn't notice this patch yet.

-- 
Markus

      reply	other threads:[~2011-07-27  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 23:32 Francesco Allertsen
2011-07-27  6:35 ` Markus Trippelsdorf [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=20110727063559.GB1641@x4.trippels.de \
    --to=markus@trippelsdorf.de \
    --cc=aelder@sgi.com \
    --cc=dchinner@redhat.com \
    --cc=fallertsen@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xfs-masters@oss.sgi.com \
    --cc=xfs@oss.sgi.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®