public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Adam Wozniak <adam.wozniak@comdev.cc>
Cc: linux-mtd@lists.infradead.org, ateam@comdev.cc
Subject: Re: need help interpreting debug output from JFFS2
Date: Fri, 18 Jan 2002 16:55:20 +0000	[thread overview]
Message-ID: <28158.1011372920@redhat.com> (raw)
In-Reply-To: <3C48504B.68F8FE7F@comdev.cc>

adam.wozniak@comdev.cc said:
>  Still tracking problems.  I've set JFFS2 debug level to 1. Does the
> output below indicate any horrible evil bugginess or
> unrecoverableness? Or is it just normal chatty debugging spew? 

That lot is harmless, at first scan.

--
dwmw2

  reply	other threads:[~2002-01-18 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020118010528.A22777@swing.comdev.cc>
2002-01-18 16:41 ` need help interpreting debug output from JFFS2 Adam Wozniak
2002-01-18 16:55   ` David Woodhouse [this message]
2002-01-18 19:55     ` optimum geometry Adam Wozniak
2002-01-21 22:49       ` David Woodhouse
2002-01-22 10:21         ` Jörn Engel
2002-01-22 10:23           ` David Woodhouse
2002-01-22 12:00             ` Jörn Engel

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=28158.1011372920@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=adam.wozniak@comdev.cc \
    --cc=ateam@comdev.cc \
    --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