The patch titled uml ubd driver: allow using up to 16 UBD devices has been removed from the -mm tree. Its filename was uml-ubd-driver-allow-using-up-to-16-ubd-devices.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ Subject: uml ubd driver: allow using up to 16 UBD devices From: Paolo 'Blaisorblade' Giarrusso <blaisorblade@xxxxxxxx> With 256 minors and 16 minors used per each UBD device, we can allow the use of up to 16 UBD devices per UML. Also chnage parse_unit and leave to the caller (which already do it) the check for excess numbers, since this is just supposed to do raw parsing. Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@xxxxxxxx> Cc: Jeff Dike <jdike@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- arch/um/drivers/ubd_kern.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN arch/um/drivers/ubd_kern.c~uml-ubd-driver-allow-using-up-to-16-ubd-devices arch/um/drivers/ubd_kern.c --- a/arch/um/drivers/ubd_kern.c~uml-ubd-driver-allow-using-up-to-16-ubd-devices +++ a/arch/um/drivers/ubd_kern.c @@ -117,7 +117,7 @@ static int ubd_ioctl(struct inode * inod unsigned int cmd, unsigned long arg); static int ubd_getgeo(struct block_device *bdev, struct hd_geometry *geo); -#define MAX_DEV (8) +#define MAX_DEV (16) static struct block_device_operations ubd_blops = { .owner = THIS_MODULE, @@ -277,7 +277,7 @@ static int parse_unit(char **ptr) return(-1); *ptr = end; } - else if (('a' <= *str) && (*str <= 'h')) { + else if (('a' <= *str) && (*str <= 'z')) { n = *str - 'a'; str++; *ptr = str; _ Patches currently in -mm which might be from blaisorblade@xxxxxxxx are origin.patch make-x86_64-udelay-round-up-instead-of-down.patch i386-x86_64-comment-magic-constants-in-delayh.patch uml-fix-prototypes.patch uml-make-execvp-safe-for-our-usage.patch tty-switch-to-ktermios-uml-fix.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html