* warning or debug text ?
@ 2001-08-29 18:49 Kenneth Johansson
2001-08-29 20:43 ` David Woodhouse
0 siblings, 1 reply; 2+ messages in thread
From: Kenneth Johansson @ 2001-08-29 18:49 UTC (permalink / raw)
To: mtd@infradead.org
in cfi_cmdset_0002.c I hit this line a lot when I created the feedback loop
with the log file on a jffs2 partition.. I don't see is so often now but
still is it needed??
printk("Waiting for chip to read, status = %d\n", chip->state);
It's a few printk in this file that has nothing indication the type of the
message and no text informing the user on what subsystem it's comming from.
In the mtd subsystem it's ALOT of this. Should I just add KERN_DEBUG to
everything ?? It's not nice to get stuff on the console when it's only a
warning or debug info.
--
Kenneth Johansson
Ericsson Business Innovation AB Tel: +46 8 404 71 83
Viderögatan 3 Fax: +46 8 404 72 72
164 80 Stockholm kenneth.johansson@inn.ericsson.se
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: warning or debug text ?
2001-08-29 18:49 warning or debug text ? Kenneth Johansson
@ 2001-08-29 20:43 ` David Woodhouse
0 siblings, 0 replies; 2+ messages in thread
From: David Woodhouse @ 2001-08-29 20:43 UTC (permalink / raw)
To: Kenneth Johansson; +Cc: mtd@infradead.org
kenneth.johansson@inn.ericsson.se said:
> In the mtd subsystem it's ALOT of this. Should I just add KERN_DEBUG
> to everything ?? It's not nice to get stuff on the console when it's
> only a warning or debug info.
Making them KERN_DEBUG or better still putting them inside some kind of
DEBUG macro like the ones in some other files would be useful. If you do
this, please could you let me have a patch?
--
dwmw2
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-08-29 20:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-08-29 18:49 warning or debug text ? Kenneth Johansson
2001-08-29 20:43 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox