From: Andi Kleen <andi@firstfloor.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] ext4: Change all super.c messages to print the device
Date: Thu, 4 Jun 2009 20:17:56 +0200 [thread overview]
Message-ID: <20090604181756.GF1065@one.firstfloor.org> (raw)
In-Reply-To: <20090604180415.GC13639@mit.edu>
On Thu, Jun 04, 2009 at 02:04:15PM -0400, Theodore Tso wrote:
> On Wed, May 20, 2009 at 04:32:01PM -0500, Eric Sandeen wrote:
> > Do the same for ext4 as Andi did for ext3:
> >
> > "This patch changes ext4 super.c to include the device name with all
> > warning/error messages, by using a new utility function ext4_msg.
> > It's a rather large patch, but very mechanic. I left debug printks
> > alone."
>
> I've added this to the ext4 patch queue.
And how about the ext3 patch?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-06-04 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 21:32 [PATCH] ext4: Change all super.c messages to print the device Eric Sandeen
2009-06-04 18:04 ` Theodore Tso
2009-06-04 18:17 ` Andi Kleen [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=20090604181756.GF1065@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).