public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jhf@rivenstone.net (Joseph Fannin)
To: tytso@mit.edu, linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: [PATCH] [BK] 0/11  Ext2/3 Updates: Extended attributes, ACL, etc.
Date: Thu, 31 Oct 2002 20:06:07 -0500	[thread overview]
Message-ID: <20021101010607.GC1683@rivenstone.net> (raw)
In-Reply-To: <20021101004751.GB1683@rivenstone.net>

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

On Thu, Oct 31, 2002 at 07:47:51PM -0500, Joseph Fannin wrote:
> On Thu, Oct 31, 2002 at 07:24:19PM -0500, Joseph Fannin wrote:
> > On Thu, Oct 31, 2002 at 03:28:29AM -0500, tytso@mit.edu wrote:
> > > Hi Linus,
> > > 
> > > I've updated the ext2/3 patches for 2.5.45.  All of these changes can
> > > also be grabbed by pulling from:
> > > 
> > > 	bk://extfs.bkbits.net/extfs-2.5-update
> 
> [build error]
> 
>     Okay, this looks like it's a problem with the transition to
> kconfig.  I have ext3 built in and ext2 built as a module, but
> CONFIG_FS_MBCACHE=m.  So the problem would be this bit, right?
> 
> # Meta block cache for Extended Attributes (ext2/ext3)
> config FS_MBCACHE
>        tristate
>        depends on EXT2_FS_XATTR || EXT3_FS_XATTR
>        default m if EXT2_FS=m || EXT3_FS=m
>        default y if EXT2_FS=y || EXT3_FS=y
> 
>     Which looks right -- it depends on either ext2 or ext3, and needs
> to be built in if either of ext2 or ext3 are, but if both are modular
> (or one is modular and the other is not built) then FS_MBCACHE should
> be modular.  But it doesn't work.

    Okay, sorry for all the mails.

    "If multiple default statements are visible only the first is
used."

    So the two default lines above need to be reversed.  This seems
backwards to me (the last should be used), but I've said enough.

-- 
Joseph Fannin
jhf@rivenstone.net

"For future reference - don't anybody else try to send patches as vi
scripts, please. Yes, it's manly, but let's face it, so is bungee-jumping
with the cord tied to your testicles." -- Linus Torvalds

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-11-01  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  8:28 [PATCH] [BK] 0/11 Ext2/3 Updates: Extended attributes, ACL, etc tytso
2002-11-01  0:24 ` Joseph Fannin
2002-11-01  0:47   ` Joseph Fannin
2002-11-01  1:06     ` Joseph Fannin [this message]
2002-11-01 11:56       ` Roman Zippel
2002-11-01 17:28         ` [PATCH] Fix 2.5-bk build error Joseph Fannin
2002-11-02  6:54           ` Theodore Ts'o
2002-11-02 11:53             ` Roman Zippel

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=20021101010607.GC1683@rivenstone.net \
    --to=jhf@rivenstone.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=zippel@linux-m68k.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