Can PYSMAP_COMPAT go?

[Wolfram Sang]

Hi,

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?

Regards,

   Wolfram

[1] http://marc.info/?l=linux-kernel&m=127024096210230&w=2

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20100420/7d096e86/attachment-0001.sig>