cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] dlm & gfs2: use sysfs
Date: Fri, 26 Jan 2007 12:09:09 +0000	[thread overview]
Message-ID: <1169813349.11001.127.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20070125184239.86d38bd9.rdunlap@xenotime.net>

Hi,

Now in the GFS2 -nmw git tree. Thanks,

Steve.

On Thu, 2007-01-25 at 18:42 -0800, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> With CONFIG_DLM=m, CONFIG_PROC_FS=n, and CONFIG_SYSFS=n, kernel build
> fails with:
> 
> WARNING: "kernel_subsys" [fs/gfs2/locking/dlm/lock_dlm.ko] undefined!
> WARNING: "kernel_subsys" [fs/dlm/dlm.ko] undefined!
> WARNING: "kernel_subsys" [fs/configfs/configfs.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> 
> Since fs/dlm/lockspace.c and fs/gfs2/locking/dlm/sysfs.c use
> kernel_subsys, they should either DEPEND on it or SELECT it.
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  fs/dlm/Kconfig  |    1 +
>  fs/gfs2/Kconfig |    1 +
>  2 files changed, 2 insertions(+)
> 
> --- linux-2620-rc6.orig/fs/dlm/Kconfig
> +++ linux-2620-rc6/fs/dlm/Kconfig
> @@ -5,6 +5,7 @@ config DLM
>  	tristate "Distributed Lock Manager (DLM)"
>  	depends on IPV6 || IPV6=n
>  	select CONFIGFS_FS
> +	select SYSFS
>  	select IP_SCTP if DLM_SCTP
>  	help
>  	A general purpose distributed lock manager for kernel or userspace
> --- linux-2620-rc6.orig/fs/gfs2/Kconfig
> +++ linux-2620-rc6/fs/gfs2/Kconfig
> @@ -38,6 +38,7 @@ config GFS2_FS_LOCKING_DLM
>  	select IP_SCTP if DLM_SCTP
>  	select CONFIGFS_FS
>  	select DLM
> +	select SYSFS
>  	help
>  	Multiple node locking module for GFS2
>  
> 



           reply	other threads:[~2007-01-26 12:09 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20070125184239.86d38bd9.rdunlap@xenotime.net>]

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=1169813349.11001.127.camel@quoit.chygwyn.com \
    --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 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).