cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Copy i_flags to gfs2 inode flags on write
Date: Mon, 23 Apr 2007 20:41:34 +0200	[thread overview]
Message-ID: <20070423184134.GD6029@duck.suse.cz> (raw)

  Hi,

  attached is a patch to copy i_flags to GFS2 specific i_di_di_flags. The
patch is compile-tested only. Steven, does it look OK to you?

								Honza

-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2-2.6.21-rc6-propagate_flags.diff
Type: text/x-patch
Size: 4621 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070423/d9dceb72/attachment.bin>

             reply	other threads:[~2007-04-23 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 18:41 Jan Kara [this message]
2007-04-24 10:05 ` [Cluster-devel] Re: [PATCH] Copy i_flags to gfs2 inode flags on write Steven Whitehouse
2007-04-26  8:06   ` Jan Kara

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=20070423184134.GD6029@duck.suse.cz \
    --to=jack@suse.cz \
    /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).