From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] - GFS2: Fix typo in stuffed file data copy handling
Date: Fri, 30 Jul 2010 11:34:52 -0400 (EDT) [thread overview]
Message-ID: <177836242.877301280504092276.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <678281826.877281280504086845.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
trunc_start() in bmap.c incorrectly uses sizeof(struct gfs2_inode) instead of
sizeof(struct gfs2_dinode).
Signed-off-by: Abhi Das <adas@redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz619810.patch
Type: text/x-patch
Size: 466 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20100730/9e73afd5/attachment.bin>
next parent reply other threads:[~2010-07-30 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <678281826.877281280504086845.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-07-30 15:34 ` Abhijith Das [this message]
2010-07-30 16:01 ` [Cluster-devel] [GFS2 PATCH] - GFS2: Fix typo in stuffed file data copy handling 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=177836242.877301280504092276.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=adas@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 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).