From: Theodore Tso <tytso@mit.edu>
To: Curt Wohlgemuth <curtw@google.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: fix ext4_dirty_inode() compile warning
Date: Fri, 2 Oct 2009 21:09:01 -0400 [thread overview]
Message-ID: <20091003010901.GB11365@mit.edu> (raw)
In-Reply-To: <6601abe90910020922g4e6a59e7mcc4eeda5cd7b4d1f@mail.gmail.com>
On Fri, Oct 02, 2009 at 09:22:18AM -0700, Curt Wohlgemuth wrote:
> Hi Ted:
>
> Apparently my patch for
>
> ext4: Make sure ext4_dirty_inode() updates the inode in no journal mode
>
> didn't play well if CONFIG_JBD_DEBUG wasn't defined.
>
> Here are two patches that fix it. I don't know if the jbd_debug() call has
> any importance or not; you can choose which is better perhaps?
I chose the first one, with a slightly elaborated commit message.
Thanks,
- Ted
prev parent reply other threads:[~2009-10-03 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 16:22 [PATCH] ext4: fix ext4_dirty_inode() compile warning Curt Wohlgemuth
2009-10-03 1:09 ` 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=20091003010901.GB11365@mit.edu \
--to=tytso@mit.edu \
--cc=curtw@google.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 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).