From: David Woodhouse <dwmw2@infradead.org>
To: torvalds@osdl.org, akpm@osdl.org, kronos@kronoz.cjb.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6.8-rc2] Fix JFFS2_COMPRESSION_OPTIONS in Kconfig
Date: Tue, 20 Jul 2004 13:24:59 -0400 [thread overview]
Message-ID: <1090344299.4189.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20040719154145.GA5429@dreamland.darkstar.lan>
On Mon, 2004-07-19 at 17:41 +0200, Kronos wrote:
> Hi,
> It seems to me that JFFS2_COMPRESSION_OPTIONS depends on JFFS2_FS:
Indeed it does.
Linus/Andrew, please pull from bk://linux-mtd.bkbits.net/mtd-2.6.
It has Kronos' fix and a couple more from Adrian Bunk, and it also marks
the JFFS2 support for NAND flash as no longer being experimental.
ChangeSet@1.1852, 2004-07-20 12:42:36-04:00, dwmw2@shinybook.infradead.org +1 -0
NAND support in JFFS2 isn't experimental any more.
ChangeSet@1.1851, 2004-07-20 12:40:06-04:00, kronos@kronoz.cjb.net +1 -0
Fix JFFS2_COMPRESSION_OPTIONS in Kconfig
Hi,
It seems to me that JFFS2_COMPRESSION_OPTIONS depends on JFFS2_FS:
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
ChangeSet@1.1850, 2004-07-20 12:37:20-04:00, bunk@fs.tum.de +1 -0
MAINTAINERS: update MTD list
Trying to send an email to mtd@infradead.org gives you the answer that
you should use linux-mtd@lists.infradead.org instead.
So let's update the entry in MAINTAINERS.
Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
ChangeSet@1.1849, 2004-07-20 12:35:52-04:00, bunk@fs.tum.de +5 -0
MTD: remove some kernel 2.0 and 2.2 #ifdef's
The patch below (applies against 2.6.8-rc2) removes some #ifdef's for
kernel 2.0 and 2.2 from the MTD code.
Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
--
dwmw2
prev parent reply other threads:[~2004-07-20 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 15:41 [PATCH][2.6.8-rc2] Fix JFFS2_COMPRESSION_OPTIONS in Kconfig Kronos
2004-07-20 17:24 ` David Woodhouse [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=1090344299.4189.3.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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