Hi, I am looking over the "[RFC] mmcoops with panic/oops" and is strikes me that although platform data is used to limit the area of the MMC device to which the oops is witten, the entire device has to belong (be bound to) the mmc_oops driver and as such no part of the device can be used for anything else. I am wondering if I am missing something? In particular, I would like to allow a single MMC chip to be used both by mmcblk (as a filesystem) and as mmc_oops (a small area reserved for writing oops messages). -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
