From: Alexey Fisher <bug-track@fisher-privat.net>
To: linux-ext4@vger.kernel.org
Subject: one way to dmesg
Date: Wed, 04 Nov 2009 15:26:44 +0100 [thread overview]
Message-ID: <1257344804.2852.11.camel@zwerg> (raw)
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.
Firs question: is it really important to print function in ext3_warning?
Or is it just ok to do it ext4_msg way?
Alexey
next reply other threads:[~2009-11-04 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 14:26 Alexey Fisher [this message]
2009-11-04 15:18 ` one way to dmesg Greg Freemyer
2009-11-04 15:29 ` Alexey Fisher
2009-11-04 15:46 ` Greg Freemyer
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=1257344804.2852.11.camel@zwerg \
--to=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