Can PYSMAP_COMPAT go?
w.sang at pengutronix.de
Tue Apr 20 02:35:47 EDT 2010
triggered by bug-report #15729 (thread at ), 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
Grepping for current users:
~/Kernel/linux-2.6/arch$ grep -r 'MAP_COMPAT' * | grep -v 'is not set'
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?
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
More information about the linux-mtd