All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Valerie Clement <Valerie.Clement@bull.net>, linux-ext4@vger.kernel.org
Subject: Re: [RFC][PATCH 4/4] BIG_BG: block group descriptor modifications
Date: Thu, 30 Nov 2006 14:49:49 -0500	[thread overview]
Message-ID: <20061130194949.GC10999@thunk.org> (raw)
In-Reply-To: <20061125092346.GA4241@schatzie.adilger.int>

On Sat, Nov 25, 2006 at 02:23:46AM -0700, Andreas Dilger wrote:
> Also note that the on-disk layout of this struct in e2fsprogs is a bit
> incorrect - it has the above 3 __u16, but then immediately __u32 bg_reserved
> so those fields are padded incorrectly.  I think it isn't a fatal problem,
> just something to be aware of and fix.

Thanks for pointing this out; I've fixed this in Mercurial repository
for e2fsprogs.

						- Ted

      parent reply	other threads:[~2006-11-30 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 16:48 [RFC][PATCH 4/4] BIG_BG: block group descriptor modifications Valerie Clement
2006-11-25  9:23 ` Andreas Dilger
2006-11-30 16:04   ` Valerie Clement
2006-11-30 19:49   ` Theodore Tso [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=20061130194949.GC10999@thunk.org \
    --to=tytso@mit.edu \
    --cc=Valerie.Clement@bull.net \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.