public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 0/7] xfs: xfs_log_recover.c cleanups
Date: Fri, 09 Apr 2010 17:26:04 -0500	[thread overview]
Message-ID: <1270851964.7840.120.camel@doink> (raw)
In-Reply-To: <201003182253.o2IMrfX0001827@stout.americas.sgi.com>

On Thu, 2010-03-18 at 17:53 -0500, Alex Elder wrote:
> This series of patches contains a set of changes primarily in
> the file "fs/xfs/xfs_log_recover.c".  They're mostly cleanup
> patches, but one of them fixes a bug in two spots.

I'm re-submitting this series of patches.  A few of them
are unchanged (already reviewed by Christoph Hellwig).
I have addressed a few other comments he made:
- Only encapsulate the validity check, not the reporting
  of errors, in the 5th patch
- The 7th "odds and ends" patch has been broken into
  several smaller patches, each with its own explanation.
  A few changes have been removed for now.
- Added another patch to the series that gets rid of
  the l_sectbb_log (which holds the log-base-2 of
  the number of basic blocks in a log sector), and
  in its places uses l_sectsize (the number of basic
  blocks in a log sector).

There are now 10 patches in the series.  I've indicated
the patches that involve changes from before (possibly
pulled into a separate patch) with "PATCHv2".

					-Alex

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-04-09 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 22:53 [PATCH 0/7] xfs: xfs_log_recover.c cleanups Alex Elder
2010-04-09 22:26 ` Alex Elder [this message]

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=1270851964.7840.120.camel@doink \
    --to=aelder@sgi.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