linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make cramfs look less hostile
Date: Sun, 15 Jun 2003 19:17:20 +0200	[thread overview]
Message-ID: <20030615171719.GE1063@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306151245070.29663-100000@coffee.psychology.mcmaster.ca>

On Sun, 15 June 2003 12:46:26 -0400, Mark Hahn wrote:
> 
> > This thing has been biting me now and again.  "cramfs: wrong magic\n"
> > looks like an error condition to most people and thus creates bug
> > reports.  But there is no bug per se in having cramfs support in the
> > kernel and booting from a jffs2 rootfs.  So instead of teaching the
> > users over and over, how about this little one-liner?
> 
> good argument.  but I was expecting you to remove the message entirely,
> or else make it *really* explanatory like "OK, not cramfs then"

Well, some embedded people trying to get this shiny new hardware with
bad debugging interfaces up and running might still like that printk.
But it would make sense to wrap it behind CONFIG_CRAMFS_DEBUG or
#define DEBUG 1 inside inode.c

Comments?

Jörn

-- 
Optimizations always bust things, because all optimizations are, in
the long haul, a form of cheating, and cheaters eventually get caught.
-- Larry Wall 

  parent reply	other threads:[~2003-06-15 17:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 16:05 [PATCH] make cramfs look less hostile Jörn Engel
     [not found] ` <Pine.LNX.4.44.0306151245070.29663-100000@coffee.psychology.mcmaster.ca>
2003-06-15 17:17   ` Jörn Engel [this message]
     [not found] ` <200306151157.10493.brian@mdrx.com>
2003-06-15 17:19   ` Jörn Engel
2003-06-15 17:26 ` Christoph Hellwig
2003-06-15 17:39   ` Jörn Engel
2003-06-15 17:44     ` Christoph Hellwig
2003-06-15 17:58       ` Jörn Engel
2003-06-15 18:03         ` Christoph Hellwig
2003-06-15 18:14           ` Jörn Engel
2003-06-15 18:18             ` Christoph Hellwig
2003-06-15 21:49               ` Andries Brouwer
2003-06-16  9:12                 ` Jörn Engel
2003-06-16 11:21                   ` Andries Brouwer
2003-06-16 11:37                     ` Jörn Engel
2003-06-18  0:24             ` Robert White
2003-06-15 17:27 ` Jörn Engel
2003-06-16  5:54   ` H. Peter Anvin
     [not found] <20030615161009$6dde@gated-at.bofh.it>
     [not found] ` <20030615174004$76d0@gated-at.bofh.it>
     [not found]   ` <20030615175007$7f59@gated-at.bofh.it>
     [not found]     ` <20030615175012$0573@gated-at.bofh.it>
     [not found]       ` <20030615181004$3663@gated-at.bofh.it>
     [not found]         ` <20030615181010$7f10@gated-at.bofh.it>
     [not found]           ` <20030615182013$7a4e@gated-at.bofh.it>
     [not found]             ` <20030615183011$3fc0@gated-at.bofh.it>
2003-06-15 21:20               ` Pascal Schmidt
2003-06-16  5:37                 ` Christoph Hellwig

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=20030615171719.GE1063@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).