From: David Woodhouse <dwmw2@infradead.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Satyam Sharma <satyam.sharma@gmail.com>,
Richard Purdie <rpurdie@openedhand.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] jffs2: Add LZO compression support to jffs2
Date: Fri, 04 May 2007 13:47:32 +0100 [thread overview]
Message-ID: <1178282852.11120.282.camel@pmac.infradead.org> (raw)
In-Reply-To: <20070504144146.6a91d974@dhcp-252-105.norway.atmel.com>
On Fri, 2007-05-04 at 14:41 +0200, Haavard Skinnemoen wrote:
>
> Hmm...everything else in lib/Kconfig is supposed to be _selected_, not
> depended upon. And the only three items in there which can actually be
> selected by the user all begin their helptexts with
>
> "This option is provided for the case where no in-kernel-tree modules
> require FOO functions".
>
> Are you sure it's a good idea to break with existing practice? I'm
> concerned that nobody will ever find the JFFS2_LZO option if it means
> they will have to go all the way down to the "Library functions" menu
> and select something to make the option visible...
That would seem be a tools problem.
Nevertheless, if I merge it with 'select', won't it break while the core
LZO patches aren't yet upstream?
Of course, one could argue that that's also a tools problem. All this
proliferation of 'select' is doing is moving problems around rather than
solving them.
--
dwmw2
next prev parent reply other threads:[~2007-05-04 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 11:30 [PATCH 2/5] jffs2: Add LZO compression support to jffs2 Richard Purdie
2007-05-04 11:35 ` David Woodhouse
2007-05-04 12:41 ` Haavard Skinnemoen
2007-05-04 12:47 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-04 11:45 Richard Purdie
2007-05-01 14:47 Richard Purdie
2007-05-01 20:00 ` Randy Dunlap
2007-05-04 9:06 ` Satyam Sharma
2007-05-04 10:52 ` Richard Purdie
2007-02-28 19:13 Richard Purdie
2007-04-25 12:35 ` David Woodhouse
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=1178282852.11120.282.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=randy.dunlap@oracle.com \
--cc=rpurdie@openedhand.com \
--cc=satyam.sharma@gmail.com \
/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