linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	swhiteho@redhat.com, cluster-devel@redhat.com
Subject: Re: linux-next: Tree for January 13 (gfs2 build error)
Date: Tue, 13 Jan 2009 13:31:40 -0800	[thread overview]
Message-ID: <496D083C.3060109@oracle.com> (raw)
In-Reply-To: <20090113175145.cdfa9c6a.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi all,
> 
> Today, I merged the updates to Linus' and the powerpc trees that happened
> during the day.
> 
> Changes since 20090112:


When CONFIG_FILE_LOCKING=n, this construct:

	.setlease	= generic_setlease,

refers to a macro, not a function, so the address of it
fails with:

fs/gfs2/ops_file.c:746: error: 'generic_
setlease' undeclared here (not in a function)

-- 
~Randy

      parent reply	other threads:[~2009-01-13 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  6:51 linux-next: Tree for January 13 Stephen Rothwell
2009-01-13 11:30 ` [BUILD-FAILURE] next-20090113 - powerpc - kernel/idle.c fails at cpu_idle() Kamalesh Babulal
2009-01-13 23:18   ` Stephen Rothwell
2009-01-13 12:03 ` [BUILD-FAILURE] next-20090113 - drivers/scsi/aha1542.c builds with CONFIG_PPC=y Kamalesh Babulal
2009-01-13 17:50   ` James Bottomley
2009-01-13 23:19   ` Stephen Rothwell
2009-01-13 13:02 ` [PATCH] next-20090113 - scsi_debug fails with CONFIG_CRC_T10DIF=n Kamalesh Babulal
2009-01-13 17:51   ` James Bottomley
2009-01-13 21:31 ` Randy Dunlap [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=496D083C.3060109@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).