Can PYSMAP_COMPAT go?

[Lennert Buytenhek]

On Tue, Apr 20, 2010 at 08:35:47AM +0200, Wolfram Sang wrote:

> triggered by bug-report #15729 (thread at [1]), I wondered where default "0"
> for MTD_PHYSMAP_LEN came from and found
> 73566edf9b91dd085ddb12033d0ea7288979dd10. Its description says:
> 
>     Once all physmap users have been converted to instantiate their own
>     platform devices, the compat code can go.  (Or we decide that we can
>     change all the in-tree users at the same time, and never merge the
>     compat code.)
> 
> Grepping for current users:
> 
> ~/Kernel/linux-2.6/arch$ grep -r 'MAP_COMPAT' * | grep -v 'is not set'
> sh/configs/polaris_defconfig:CONFIG_MTD_PHYSMAP_COMPAT=y
> 
> This one could be fixed and then the compat code could be removed. I'd pick up
> the job, if I get a sign that this has a chance to go in. Or shall compat stay
> for a reason?

COMPAT needs to die.  There are at least two other ways of specifying
the same info (device tree or manual instantiation of a platform device
from your platform code), and we really shouldn't allow specifying this
in the .config as that will just give people other crazy ideas.