From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3] Split version of xfs_swap_extents bug fix
Date: Thu, 14 Jan 2010 12:33:53 +1100 [thread overview]
Message-ID: <1263432836-13368-1-git-send-email-david@fromorbit.com> (raw)
This splits the swap extents bug fix into three patches as requested
the bug fix, the tracing code and the variable name cleanup. Apart from
splitting the patch, the only change is in the cleanup patch which makes
xfs_swap_extents() static.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-01-14 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 1:33 Dave Chinner [this message]
2010-01-14 1:33 ` [PATCH 1/3] xfs: xfs_swap_extents needs to handle dynamic fork offsets Dave Chinner
2010-01-14 6:42 ` Christoph Hellwig
2010-01-14 1:33 ` [PATCH 2/3] xfs: add tracing to xfs_swap_extents Dave Chinner
2010-01-14 1:33 ` [PATCH 3/3] xfs: clean up inconsistent variable naming in xfs_swap_extent Dave Chinner
2010-01-14 15:41 ` [PATCH 3/3] xfs: clean up inconsistent variable naming inxfs_swap_extent Alex Elder
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=1263432836-13368-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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