public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 prints
Date: Sat, 13 Nov 2004 11:38:19 +0000	[thread overview]
Message-ID: <1100345900.8015.17.camel@localhost.localdomain> (raw)
In-Reply-To: <4195EF83.8050104@yandex.ru>

On Sat, 2004-11-13 at 14:26 +0300, Artem B. Bityuckiy wrote:
> But the main thing why I think it would be nice to introduce macros like 
> these is that the messages will be a bit standard. I mean that all 
> errors will have the same prefix. It is useful when you develop JFFS2 
> with debugging output on. In this case you will just s/JFFS2 Error and 
> see all the error messages. But currently, it is hard to find all the 
> error messages in JFFS2 because some of them use prefix "Error", some 
> just contain the word "failed", etc.

I'm not sure that just a standard prefix will really help with
debugging. The trick is still to know what's important, and what's
noise. And running it with full debugging is slow enough already over a
115200 baud serial line, without adding more stuff to each line :)

I'd much rather see an effort to weed out the unnecessary prints at
debug level 1, moving them to level 2. I don't consider level 2 to be
particularly useful in general; it's _too_ verbose. 

-- 
dwmw2

  reply	other threads:[~2004-11-13 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13 11:26 JFFS2 prints Artem B. Bityuckiy
2004-11-13 11:38 ` David Woodhouse [this message]
2004-11-13 11:56   ` Artem B. Bityuckiy

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=1100345900.8015.17.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=abityuckiy@yandex.ru \
    --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