mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com,
	"Toralf Förster" <toralf.foerster@gmx.de>
Subject: Re: [GFS2] Fix Kconfig wrt CRC32 [8/9]
Date: Fri, 24 Nov 2006 21:43:38 -0800	[thread overview]
Message-ID: <20061124214338.0e4d0510.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1164360889.3392.146.camel@quoit.chygwyn.com>

On Fri, 24 Nov 2006 09:34:49 +0000 Steven Whitehouse wrote:

> >From 6f788fd00c82533d4cd5587a9706f8468658a24d Mon Sep 17 00:00:00 2001
> From: Steven Whitehouse <swhiteho@redhat.com>
> Date: Mon, 20 Nov 2006 10:04:49 -0500
> Subject: [PATCH] [GFS2] Fix Kconfig wrt CRC32
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> GFS2 requires the CRC32 library function. This was reported by
> Toralf Förster.
> 
> Cc: Toralf Förster <toralf.foerster@gmx.de>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> ---
>  fs/gfs2/Kconfig |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/gfs2/Kconfig b/fs/gfs2/Kconfig
> index 8c27de8..c0791cb 100644
> --- a/fs/gfs2/Kconfig
> +++ b/fs/gfs2/Kconfig
> @@ -2,6 +2,7 @@ config GFS2_FS
>  	tristate "GFS2 file system support"
>  	depends on EXPERIMENTAL
>  	select FS_POSIX_ACL
> +	select CRC32
>  	help
>  	A cluster filesystem.

Hi,

Do you also have Kconfig patches for DLM needing SYSFS
and DLM needing CONFIG_NET ?

---
~Randy

  reply	other threads:[~2006-11-25  5:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24  9:34 Steven Whitehouse
2006-11-25  5:43 ` Randy Dunlap [this message]
2006-11-27 13:24   ` Steven Whitehouse
2006-11-27 16:38     ` Randy Dunlap
2006-11-28 18:02       ` Steven Whitehouse
2006-11-28 18:33         ` Randy Dunlap
2006-11-29  9:57           ` 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=20061124214338.0e4d0510.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    --cc=toralf.foerster@gmx.de \
    /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

Powered by JetHome