public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: tytso@mit.edu
Cc: Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org
Subject: Re: Unify log messages in ext4
Date: Mon, 23 Nov 2009 16:11:58 +0100	[thread overview]
Message-ID: <1258989118.2841.2.camel@mini> (raw)
In-Reply-To: <20091123141108.GC2532@thunk.org>

Am Montag, den 23.11.2009, 09:11 -0500 schrieb tytso@mit.edu:
> On Mon, Nov 23, 2009 at 12:55:14PM +0100, Jan Kara wrote:
> > On Mon 23-11-09 12:45:36, Alexey Fisher wrote:
> > > Am Montag, den 23.11.2009, 11:36 +0100 schrieb Jan Kara:
> > > > Thanks for the patch. I've merged it into my tree just with the following
> > > > typo fixes.
> > > 
> > > Thank you,
> > > are there any ext4 patches around? Or this will be my next step. 
> >   I'm not aware of them...
> 
> Ext4 is using ext4_msg() already.  Eric Sandeen added it a while ago,
> and the idea to convert ext2 and ext4 to use ext2_msg() and ext3_msg()
> came from ext4.

O, yeah..
i greped ext4/super.c and there is no mach left.
now i have most i need from ext[234],

Thank you,
	Alexey


  reply	other threads:[~2009-11-23 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21 10:25 [PATCH v1] Unify log messages in ext3 Alexey Fisher
2009-11-21 23:55 ` Eric Sandeen
2009-11-22 19:12   ` Alexey Fisher
2009-11-22 19:38   ` [PATCH v2] " Alexey Fisher
2009-11-22 19:42     ` Alexey Fisher
2009-11-23 10:36     ` Jan Kara
2009-11-23 11:45       ` Unify log messages in ext4 Alexey Fisher
2009-11-23 11:55         ` Jan Kara
2009-11-23 14:11           ` tytso
2009-11-23 15:11             ` Alexey Fisher [this message]
2009-11-23 16:16             ` Eric Sandeen

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=1258989118.2841.2.camel@mini \
    --to=bug-track@fisher-privat.net \
    --cc=adilger@sun.com \
    --cc=jack@suse.cz \
    --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