All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: mmotm 2009-01-14-20-31 uploaded (gfs2)
Date: Fri, 16 Jan 2009 10:20:03 +0000	[thread overview]
Message-ID: <1232101203.3554.3.camel@localhost.localdomain> (raw)
In-Reply-To: <496F8AED.3020604@oracle.com>

Hi,

On Thu, 2009-01-15 at 11:13 -0800, Randy Dunlap wrote:
> akpm at linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-01-14-20-31 has been uploaded to
> > 
> >    http://userweb.kernel.org/~akpm/mmotm/
> > 
> > and will soon be available at
> > 
> >    git://git.zen-sources.org/zen/mmotm.git
> 
> 
> when CONFIG_FILE_LOCKING=n:
> 
> mmotm-2009-0114-2031/fs/gfs2/ops_file.c:746: error: 'generic_setlease' undeclared here (not in a function)
> 
> 
> since generic_setlease() is a macro/define in that case.
> 
Hmm, it looks like I'll have to do this, in that case:

diff --git a/fs/gfs2/ops_file.c b/fs/gfs2/ops_file.c
index 99d726f..4580335 100644
--- a/fs/gfs2/ops_file.c
+++ b/fs/gfs2/ops_file.c
@@ -743,7 +743,9 @@ const struct file_operations *gfs2_file_fops_nolock = &(const struct file_operat
 	.fsync		= gfs2_fsync,
 	.splice_read	= generic_file_splice_read,
 	.splice_write	= generic_file_splice_write,
+#ifdef CONFIG_FILE_LOCKING
 	.setlease	= generic_setlease,
+#endif /* CONFIG_FILE_LOCKING */
 };
 
 const struct file_operations *gfs2_dir_fops_nolock = &(const struct file_operations){


which is not ideal, but I don't see any easy way to avoid the #ifdef,

Steve.




WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	cluster-devel@redhat.com
Subject: Re: mmotm 2009-01-14-20-31 uploaded (gfs2)
Date: Fri, 16 Jan 2009 10:20:03 +0000	[thread overview]
Message-ID: <1232101203.3554.3.camel@localhost.localdomain> (raw)
In-Reply-To: <496F8AED.3020604@oracle.com>

Hi,

On Thu, 2009-01-15 at 11:13 -0800, Randy Dunlap wrote:
> akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-01-14-20-31 has been uploaded to
> > 
> >    http://userweb.kernel.org/~akpm/mmotm/
> > 
> > and will soon be available at
> > 
> >    git://git.zen-sources.org/zen/mmotm.git
> 
> 
> when CONFIG_FILE_LOCKING=n:
> 
> mmotm-2009-0114-2031/fs/gfs2/ops_file.c:746: error: 'generic_setlease' undeclared here (not in a function)
> 
> 
> since generic_setlease() is a macro/define in that case.
> 
Hmm, it looks like I'll have to do this, in that case:

diff --git a/fs/gfs2/ops_file.c b/fs/gfs2/ops_file.c
index 99d726f..4580335 100644
--- a/fs/gfs2/ops_file.c
+++ b/fs/gfs2/ops_file.c
@@ -743,7 +743,9 @@ const struct file_operations *gfs2_file_fops_nolock = &(const struct file_operat
 	.fsync		= gfs2_fsync,
 	.splice_read	= generic_file_splice_read,
 	.splice_write	= generic_file_splice_write,
+#ifdef CONFIG_FILE_LOCKING
 	.setlease	= generic_setlease,
+#endif /* CONFIG_FILE_LOCKING */
 };
 
 const struct file_operations *gfs2_dir_fops_nolock = &(const struct file_operations){


which is not ideal, but I don't see any easy way to avoid the #ifdef,

Steve.



  reply	other threads:[~2009-01-16 10:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  4:32 mmotm 2009-01-14-20-31 uploaded akpm
2009-01-15 19:13 ` [Cluster-devel] Re: mmotm 2009-01-14-20-31 uploaded (gfs2) Randy Dunlap
2009-01-15 19:13   ` Randy Dunlap
2009-01-16 10:20   ` Steven Whitehouse [this message]
2009-01-16 10:20     ` Steven Whitehouse
2009-01-16 16:43     ` [Cluster-devel] " Andrew Morton
2009-01-16 16:43       ` Andrew Morton
2009-01-16 17:02       ` [Cluster-devel] " Steven Whitehouse
2009-01-16 17:02         ` Steven Whitehouse
2009-01-16 17:06         ` [Cluster-devel] " Randy Dunlap
2009-01-16 17:06           ` Randy Dunlap
2009-01-16 17:35           ` [Cluster-devel] " Andrew Morton
2009-01-16 17:35             ` Andrew Morton
2009-01-16 17:37             ` [Cluster-devel] " Steven Whitehouse
2009-01-16 17:37               ` Steven Whitehouse
2009-01-19 15:16             ` [Cluster-devel] " Steven Whitehouse
2009-01-19 15:16               ` Steven Whitehouse
2009-01-19 17:05               ` [Cluster-devel] " Randy Dunlap
2009-01-19 17:05                 ` Randy Dunlap
2009-01-19 17:27                 ` [Cluster-devel] " Steven Whitehouse
2009-01-19 17:27                   ` Steven Whitehouse
2009-01-19 17:55                   ` [Cluster-devel] " Randy Dunlap
2009-01-19 17:55                     ` Randy Dunlap

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=1232101203.3554.3.camel@localhost.localdomain \
    --to=swhiteho@redhat.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 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.