Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Block alloc fixes
Date: Thu, 23 Apr 2009 10:16:53 +0100	[thread overview]
Message-ID: <1240478216-2594-1-git-send-email-swhiteho@redhat.com> (raw)

These three patches fix a couple of bugs in the block allocation
code that was updated at the merge window. Thanks are due to
Benny Halevy, Christoph Lameter and Willy Tarreau for looking
at the __ffs64 patch. I've updated the comment in that patch
in the light of Willy Tarreau's suggestion,

Steve.




             reply	other threads:[~2009-04-23  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  9:16 Steven Whitehouse [this message]
2009-04-23  9:16 ` [Cluster-devel] [PATCH 1/3] bitops: Add __ffs64 bitop Steven Whitehouse
2009-04-23  9:16   ` [Cluster-devel] [PATCH 2/3] GFS2: Fix bug in block allocation Steven Whitehouse
2009-04-23  9:16     ` [Cluster-devel] [PATCH 3/3] GFS2: Ensure that the inode goal block settings are updated Steven Whitehouse
     [not found]   ` <52615.1240839635@turing-police.cc.vt.edu>
2009-04-27 15:41     ` [Cluster-devel] Re: [PATCH 1/3] bitops: Add __ffs64 bitop 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=1240478216-2594-1-git-send-email-swhiteho@redhat.com \
    --to=swhiteho@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