linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@lazybastard.org>
To: Josh Boyer <jwboyer@gmail.com>, Andrew Morton <akpm@osdl.org>,
	Jeff Garzik <jeff@garzik.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, jffs-dev@axis.com,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH/RFC] Delete JFFS (version 1)
Date: Wed, 13 Dec 2006 07:06:06 +0000	[thread overview]
Message-ID: <20061213070605.GB19825@lazybastard.org> (raw)
In-Reply-To: <20061212214904.GR5937@schatzie.adilger.int>

On Tue, 12 December 2006 14:49:04 -0700, Andreas Dilger wrote:
> 
> It would be better to have a printk in the module init, since users with
> upstream builds won't see the config help.

How many of those are there?  This is not ext3, this is a flash
filesystem.  Users are either those doing the upstream build or they
won't ever see a console.  Think DSL-Router. ;)

Jörn

-- 
Joern's library part 14:
http://www.sandpile.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-12-13 11:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 12:39 [PATCH/RFC] Delete JFFS (version 1) Jeff Garzik
2006-12-12 12:56 ` Josh Boyer
2006-12-12 13:02   ` Jeff Garzik
2006-12-12 13:06     ` Josh Boyer
2006-12-12 13:07       ` David Woodhouse
2006-12-12 13:09     ` Jeff Garzik
2006-12-12 17:01     ` Bill Nottingham
2006-12-12 17:20       ` Jeff Garzik
2006-12-12 17:28       ` Alan
2006-12-19 10:56         ` David Weinehall
2006-12-12 12:58 ` Jörn Engel
2006-12-12 17:53 ` Andrew Morton
2006-12-12 18:38   ` Josh Boyer
2006-12-12 21:49     ` Andreas Dilger
2006-12-13  7:06       ` Jörn Engel [this message]
2007-03-09 23:13 ` Stefan Monnier

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=20061213070605.GB19825@lazybastard.org \
    --to=joern@lazybastard.org \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=jeff@garzik.org \
    --cc=jffs-dev@axis.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).