All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Lynch <rusty@linux.co.intel.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH]remove ocfs_fill_super and port ocfs_read_super
Date: Tue Mar 30 11:28:09 2004	[thread overview]
Message-ID: <20040330172337.GA9975@penguin.co.intel.com> (raw)
In-Reply-To: <20040330024421.GA10672@ca-server1.us.oracle.com>

On Mon, Mar 29, 2004 at 06:44:21PM -0800, Mark Fasheh wrote:
> On Mon, Mar 29, 2004 at 03:46:03PM -0800, Rusty Lynch wrote:
> > Here is my previous patch with the ocfs_set_blocksize make inline, and the addition
> > of OCFS_MOD_[INC|DEC]_USE_COUNT
> Ok, this is in. I fixed a couple of things, one of them being the whole
> OCFS_DEC/INC_INODE_COUNT which I removed, and just put the kernel macros in
> the 2.4 read_super.

Ahh... good idea on where to put the mod inc/dec.
> 
> You'll prolly get conflicts when updating :(

Nope. I make a point of starting from a fresh tree when ever possible 
(less chance of munging up future patches)
> 
> Let me know if I messed anything up for 2.6, but I seriously doubt it :)
> 	--Mark

Works for me 
> 
> --
> Mark Fasheh
> Software Developer, Oracle Corp
> mark.fasheh@oracle.com

      reply	other threads:[~2004-03-30 11:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 21:00 [Ocfs2-devel] [PATCH]remove ocfs_fill_super and port ocfs_read_super Rusty Lynch
2004-03-26  8:35 ` Joel Becker
2004-03-26 14:47   ` Rusty Lynch
2004-03-29 15:29     ` Mark Fasheh
2004-03-29 15:32       ` Rusty Lynch
2004-03-29 16:42         ` Rusty Lynch
2004-03-29 17:06           ` Mark Fasheh
2004-03-29 17:46             ` Rusty Lynch
2004-03-29 20:44               ` Mark Fasheh
2004-03-30 11:28                 ` Rusty Lynch [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=20040330172337.GA9975@penguin.co.intel.com \
    --to=rusty@linux.co.intel.com \
    --cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.