mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	"cluster-devel@redhat.com" <cluster-devel@redhat.com>
Subject: RE: [PATCH] gfs2/inode.c: local functions should be static
Date: Mon, 26 Sep 2011 19:37:28 +0100	[thread overview]
Message-ID: <1317062248.2744.28.camel@menhir> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F001F39DBB86BD@AUSP01VMBX24.collaborationhost.net>

Hi,

On Mon, 2011-09-26 at 11:54 -0500, H Hartley Sweeten wrote:
> On Monday, September 26, 2011 1:28 AM, Steven Whitehouse wrote:
> > Hi,
> >
> > On Fri, 2011-09-23 at 15:51 -0700, H Hartley Sweeten wrote:
> >> Quiets the sparse noise:
> >> 
> >> warning: symbol 'gfs2_initxattrs' was not declared. Should it be static?
> >> 
> > Where did you find this function? It is not in the upstream gfs2 code...
> 
> linux-next next-20110831
> 
> This was the last update I pulled before git.kernel.org went down.
> 
> It looks like it was added by:
> 
> commit 9d8f13ba3f4833219e50767b022b82cd0da930eb
> Author: Mimi Zohar <zohar@linux.vnet.ibm.com>
> Date:   Mon Jun 6 15:29:25 2011 -0400
> 
>     security: new security_inode_init_security API adds function callback
> 
> If this has been removed since then please ignore.
> 
> Thanks,
> Hartley

I think it is a question of it not yet being added. You should send the
patch to Mimi so it is included in the correct patch series. Otherwise
remind me when the code is applies against is merged and I'll look at it
again then,

Steve.



      reply	other threads:[~2011-09-26 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23 22:51 H Hartley Sweeten
2011-09-26  8:27 ` Steven Whitehouse
2011-09-26 16:54   ` H Hartley Sweeten
2011-09-26 18:37     ` Steven Whitehouse [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=1317062248.2744.28.camel@menhir \
    --to=swhiteho@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®