From: Christoph Hellwig <hch@lst.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] remove ocfs2_write_blocks
Date: Tue Sep 20 15:27:17 2005 [thread overview]
Message-ID: <20050920202719.GA8021@lst.de> (raw)
In-Reply-To: <20050920202439.GE18764@ca-server1.us.oracle.com>
On Tue, Sep 20, 2005 at 01:24:39PM -0700, Mark Fasheh wrote:
> Thanks - committed.
>
> I took some liberties with the patch:
> - merged it with the newest version of buffer_head_io.c (it got some
> readonly goodness since your patch was created)
> - added a couple minor cleanups of my own
> - you forgot to update a comment, which I did
I think you lost the get_bh() that zab added after I submitted the
patch.
next prev parent reply other threads:[~2005-09-20 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 5:36 [Ocfs2-devel] [PATCH] remove ocfs2_write_blocks Christoph Hellwig
2005-09-20 15:24 ` Mark Fasheh
2005-09-20 15:27 ` Christoph Hellwig [this message]
2005-09-20 15:37 ` Mark Fasheh
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=20050920202719.GA8021@lst.de \
--to=hch@lst.de \
--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.