From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Write the log descriptor entries in the correct order
Date: Wed, 26 Nov 2014 13:59:15 -0500 (EST) [thread overview]
Message-ID: <262832853.20379531.1417028355876.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5475E3E6.8050302@redhat.com>
----- Original Message -----
> > As you can see, the blocks are reverse-sorted. This patch changes the
> > order so that they're written in sorted order. Log headers written with
> > the patch look more like this:
> Does that mean that this patch got the ordering the wrong way around then?
>
> https://git.kernel.org/cgit/linux/kernel/git/steve/gfs2-3.0-nmw.git/commit/fs/gfs2/lops.c?id=7f63257da1aeea9b2ee68f469b0f9f4a39e5dff8
>
> Steve.
No. It means I missed Ben's patch. Or maybe I've lost my mind. Sigh.
Bob
prev parent reply other threads:[~2014-11-26 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <745479724.20044713.1417010070420.JavaMail.zimbra@redhat.com>
2014-11-26 14:09 ` [Cluster-devel] [GFS2 PATCH] GFS2: Write the log descriptor entries in the correct order Bob Peterson
2014-11-26 14:29 ` Steven Whitehouse
2014-11-26 18:59 ` Bob Peterson [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=262832853.20379531.1417028355876.JavaMail.zimbra@redhat.com \
--to=rpeterso@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).