From: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
"mtd@infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2: strange output
Date: Tue, 29 Jan 2002 14:33:32 +0000 [thread overview]
Message-ID: <3C56B2BC.2E3AC6D9@cambridgebroadband.com> (raw)
In-Reply-To: 11887.1012310001@redhat.com
>
> Those messages are harmless. They're removed in non-ancient versions of the
> code. The system slows down partly due to the garbage collection, and
> partly due to the spewing of these messages.
>
Thanks, I guess I'll just comment out the printk then.
Alex
prev parent reply other threads:[~2002-01-29 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C5673A4.662CC3E6@cambridgebroadband.com>
2002-01-29 12:56 ` JFFS2: strange output Kenneth Johansson
2002-01-29 13:13 ` David Woodhouse
2002-01-29 14:33 ` Alex Zeffertt [this message]
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=3C56B2BC.2E3AC6D9@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.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