From: Greg Freemyer <greg.freemyer@gmail.com>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: one way to dmesg
Date: Wed, 4 Nov 2009 10:46:30 -0500 [thread overview]
Message-ID: <87f94c370911040746k49dce1f6ge8591f7714b8b19d@mail.gmail.com> (raw)
In-Reply-To: <1257348551.2091.1.camel@mini>
On Wed, Nov 4, 2009 at 10:29 AM, Alexey Fisher
<bug-track@fisher-privat.net> wrote:
> Am Mittwoch, den 04.11.2009, 10:18 -0500 schrieb Greg Freemyer:
>> On Wed, Nov 4, 2009 at 9:26 AM, Alexey Fisher
>> <bug-track@fisher-privat.net> wrote:
>> > Hallo,
>> > this is sort of continue of discussion about unified way to mount fs
>> > readonly.
>> > I wont to know how about dmesg/printk. I see ext[234] produce different
>> > logs on mount even it use same code. I feel like i have some time to
>> > digg in. My target is easy to parse dmesg.
>>
>> Patches for unified mount messages already exist. Various versions
>> have been posted in the last couple months.
>>
>> I don't know if they have been accepted yet or not.
>
> Can you point me this patch?
> I found only "add a message in remount/umount for ext4"
> http://patchwork.ozlabs.org/project/linux-ext4/list/?page=1
Looks like Toshiyuki Okajima is the author.
http://markmail.org/message/ghyjee2krfmgtybt was just posted in the
last day or two.
That patch only adds the new unified dmesg print to the vfs layer. I
think there were other patches that removed the scattered prints from
the various individual filesystems.
Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-04 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 14:26 one way to dmesg Alexey Fisher
2009-11-04 15:18 ` Greg Freemyer
2009-11-04 15:29 ` Alexey Fisher
2009-11-04 15:46 ` Greg Freemyer [this message]
2009-11-04 15:59 ` Alexey Fisher
2009-11-05 15:02 ` Theodore Tso
2009-11-05 15:51 ` Alexey Fisher
2009-11-04 15:19 ` Alexey Fisher
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=87f94c370911040746k49dce1f6ge8591f7714b8b19d@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=bug-track@fisher-privat.net \
--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