From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers
Date: Sun, 08 Jan 2006 13:06:20 +0000 [thread overview]
Message-ID: <1136725580.30348.69.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060108125700.GI3774@stusta.de>
On Sun, 2006-01-08 at 13:57 +0100, Adrian Bunk wrote:
> What I want for 2.6.16 is to remove the wrong dependency of MTD_SHARP on
> BROKEN and the non-compiling drivers either still hidden under BROKEN or
> removed.
>
> If there is any way I can submit a patch achieving this that would be
> acceptable for you simply tell how exactly you want this patch.
Remove the incorrect BROKEN dependency from MTD_OBSOLETE_CHIPS.
If you then want to add it again to any chip driver which really doesn't
compile, feel free. But leave the map drivers alone. Those can be
switched to use different chip back-ends.
--
dwmw2
next prev parent reply other threads:[~2006-01-08 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 22:07 [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk
2006-01-08 0:00 ` David Woodhouse
2006-01-08 0:24 ` Adrian Bunk
2006-01-08 0:38 ` David Woodhouse
2006-01-08 1:45 ` Andrew Morton
2006-01-08 12:41 ` David Woodhouse
2006-01-08 12:57 ` Adrian Bunk
2006-01-08 13:06 ` David Woodhouse [this message]
2006-01-08 14:14 ` [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN Adrian Bunk
2006-01-08 14:24 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 18:14 [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk
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=1136725580.30348.69.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--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