From: Eric Sandeen <esandeen@redhat.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: ext4 kernel patches against linux-2.6.18-rc7-mm1
Date: Wed, 20 Sep 2006 11:32:28 -0500 [thread overview]
Message-ID: <45116D1C.20807@redhat.com> (raw)
In-Reply-To: <1158767799.9276.23.camel@kleikamp.austin.ibm.com>
Dave Kleikamp wrote:
> # From Mingming Cao
> sector_t-jbd2.patch
I think this one needs to address the first, last variables in
journal_fail_superblock():
static int journal_reset(journal_t *journal)
{
journal_superblock_t *sb = journal->j_superblock;
- unsigned int first, last;
+ sector_t first, last;
first = be32_to_cpu(sb->s_first);
last = be32_to_cpu(sb->s_maxlen);
(and then later change that back to unsigned long long, in the spirit of
the patch series)
-Eric
next prev parent reply other threads:[~2006-09-20 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 15:56 ext4 kernel patches against linux-2.6.18-rc7-mm1 Dave Kleikamp
2006-09-20 16:32 ` Eric Sandeen [this message]
2006-09-20 17:38 ` Eric Sandeen
2006-09-21 15:15 ` Johann Lombardi
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 16:43 Alexandre Ratchov
2006-09-26 16:55 ` Alexandre Ratchov
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=45116D1C.20807@redhat.com \
--to=esandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@austin.ibm.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