From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bugreport: JFFS2 + EBS
Date: Tue, 13 Sep 2005 15:33:14 +0400 [thread overview]
Message-ID: <4326B8FA.5030608@yandex.ru> (raw)
In-Reply-To: <4326B6F4.1030709@inf.u-szeged.hu>
Ferenc Havasi wrote:
> And finaly it may also be more informative to set the JFFS2 debug level
> 1 to get more debug message (the summary debug messages is the most
> important for us)
I wonder, why don't you do the same trick that I did for fragtree build
messages and the like, (see debug.h) to be able on/off your summary
messages independently. Believe me, this is very handy to have a
possibility to filter unneeded flood.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-09-13 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 14:05 Bugreport: JFFS2 + EBS Simon Kallweit
2005-09-13 11:24 ` Ferenc Havasi
2005-09-13 11:33 ` Artem B. Bityuckiy [this message]
2005-09-13 11:39 ` Ferenc Havasi
2005-09-13 11:56 ` Artem B. Bityuckiy
2005-09-13 14:06 ` Konstantin Kletschke
2005-09-13 14:44 ` Konstantin Kletschke
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=4326B8FA.5030608@yandex.ru \
--to=dedekind@yandex.ru \
--cc=havasi@inf.u-szeged.hu \
--cc=linux-mtd@lists.infradead.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