From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH]
Date: Tue, 29 Jan 2008 08:30:24 +0000 [thread overview]
Message-ID: <1201595424.22038.316.camel@quoit> (raw)
In-Reply-To: <1201540557.18461.77.camel@technetium.msp.redhat.com>
Hi,
Now in the -nmw tree. Thanks,
Steve.
On Mon, 2008-01-28 at 11:15 -0600, Bob Peterson wrote:
> Hi,
>
> I noticed that the latest change to i_height got rid of the
> value from the inode dump. This patch adds it back.
>
> Regards,
>
> Bob Peterson
> Red Hat GFS
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> --
> fs/gfs2/inode.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
> index 084c741..11c5ce4 100644
> --- a/fs/gfs2/inode.c
> +++ b/fs/gfs2/inode.c
> @@ -1,6 +1,6 @@
> /*
> * Copyright (C) Sistina Software, Inc. 1997-2003 All rights reserved.
> - * Copyright (C) 2004-2006 Red Hat, Inc. All rights reserved.
> + * Copyright (C) 2004-2008 Red Hat, Inc. All rights reserved.
> *
> * This copyrighted material is made available to anyone wishing to use,
> * modify, copy, or redistribute it subject to the terms and conditions
> @@ -1435,6 +1435,7 @@ void gfs2_dinode_print(const struct gfs2_inode *ip)
> printk(KERN_INFO " di_goal_data = %llu\n",
> (unsigned long long)di->di_goal_data);
> printk(KERN_INFO " di_flags = 0x%.8X\n", di->di_flags);
> + printk(KERN_INFO " i_height = %u\n", ip->i_height);
> printk(KERN_INFO " di_depth = %u\n", di->di_depth);
> printk(KERN_INFO " di_entries = %u\n", di->di_entries);
> printk(KERN_INFO " di_eattr = %llu\n",
>
>
next prev parent reply other threads:[~2008-01-29 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 17:15 [Cluster-devel] [GFS2 PATCH] Bob Peterson
2008-01-29 8:30 ` Steven Whitehouse [this message]
[not found] <b1f512c7-59c2-48d7-9c01-7d6acbf30877@zmail12.collab.prod.int.phx2.redhat.com>
2012-02-17 14:15 ` Bob Peterson
2012-02-17 14:25 ` Steven Whitehouse
2012-02-17 14:34 ` Bob Peterson
2012-02-17 14:42 ` Steven Whitehouse
2012-02-17 15:23 ` 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=1201595424.22038.316.camel@quoit \
--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 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.