cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] linux-next: Tree for May 8 (dlm)
Date: Wed, 08 May 2013 11:04:45 -0700	[thread overview]
Message-ID: <518A93BD.3020300@infradead.org> (raw)
In-Reply-To: <20130508140122.e4747b58be4333060b7a248a@canb.auug.org.au>

On 05/07/13 21:01, Stephen Rothwell wrote:
> Hi all,
> 
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
> 
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees.   Please clean this up
> and resist the temptataion to rebase your trees on the way to your
> upstream ...
> 
> Changes since 20130506:
> 
> <crickets :-)>
> 

on x86_64:

when CONFIG_GFS2_FS_LOCKING_DLM=y and CONFIG_DLM=m:

fs/built-in.o: In function `gfs2_lock':
file.c:(.text+0xa512c): undefined reference to `dlm_posix_get'
file.c:(.text+0xa5140): undefined reference to `dlm_posix_unlock'
file.c:(.text+0xa514a): undefined reference to `dlm_posix_lock'
fs/built-in.o: In function `gdlm_cancel':
lock_dlm.c:(.text+0xb3f57): undefined reference to `dlm_unlock'
fs/built-in.o: In function `gdlm_unmount':
lock_dlm.c:(.text+0xb40ff): undefined reference to `dlm_release_lockspace'
fs/built-in.o: In function `sync_unlock.isra.4':
lock_dlm.c:(.text+0xb420d): undefined reference to `dlm_unlock'
fs/built-in.o: In function `sync_lock.isra.5':
lock_dlm.c:(.text+0xb42d9): undefined reference to `dlm_lock'
fs/built-in.o: In function `gdlm_put_lock':
lock_dlm.c:(.text+0xb45e7): undefined reference to `dlm_unlock'
fs/built-in.o: In function `gdlm_mount':
lock_dlm.c:(.text+0xb4928): undefined reference to `dlm_new_lockspace'
lock_dlm.c:(.text+0xb4c75): undefined reference to `dlm_release_lockspace'
fs/built-in.o: In function `gdlm_lock':
lock_dlm.c:(.text+0xb529f): undefined reference to `dlm_lock'



-- 
~Randy



       reply	other threads:[~2013-05-08 18:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130508140122.e4747b58be4333060b7a248a@canb.auug.org.au>
2013-05-08 18:04 ` Randy Dunlap [this message]
2013-05-08 23:47   ` [Cluster-devel] linux-next: Tree for May 8 (dlm) Stephen Rothwell
2013-05-09 16:50     ` David Teigland
2013-05-09 17:08       ` Randy Dunlap
2013-05-13  9:18         ` Steven Whitehouse
2013-05-13 16:30           ` Randy Dunlap
     [not found]             ` <51913F8B.7080201@infradead.org>
     [not found]               ` <51914045.1060900@infradead.org>
2013-05-13 19:45                 ` Randy Dunlap
2013-05-14  8:51                   ` Steven Whitehouse
2013-05-14 17:02                     ` [Cluster-devel] [PATCH -next] gfs2: fix DLM depends to fix build errors Randy Dunlap
2013-05-15 10:05                       ` Steven Whitehouse

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=518A93BD.3020300@infradead.org \
    --to=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).