Re: [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Date: Mon, 12 Dec 2005 10:38:15 +0100
On Sun, 2005-12-11 at 20:31 +0100, Adrian Bunk wrote:
> Either the depency of MTD_OBSOLETE_CHIPS on BROKEN is correct (in
> which case CONFIG_MTD_OBSOLETE_CHIPS=y wouldn't bring you anything),
> or the dependency on BROKEN is not correct and should be corrected.
>
> David, can you comment on this issue?
I don't see any justification for MTD_OBSOLETE_CHIPS depending on
BROKEN. That option covers a few of the obsolete chip drivers which
people shouldn't be using any more -- and I'm perfectly willing to
believe that one or two of those don't work any more, but if that's the
case then those individual drivers ought to be marked BROKEN (or just
removed). We shouldn't mark MTD_OBSOLETE_CHIPS broken.
I'd like to see the collie_defconfig updated to use the appropriate CFI
driver back end.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y
- From: Adrian Bunk
- Re: [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y
- From: Russell King
- Re: [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y
- From: Adrian Bunk
- [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y
- Prev by Date: Re: [patch 3/17] s390: move s390_root_dev_* out of the cio layer.
- Next by Date: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- Previous by thread: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
- Next by thread: [RFC: 2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers
- Index(es):
Relevant Pages
|
