The patch titled
Char: mxser_new, CMSPAR is defined
has been added to the -mm tree. Its filename is
char-mxser_new-cmspar-is-defined.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: Char: mxser_new, CMSPAR is defined
From: Jiri Slaby <jirislaby@xxxxxxxxx>
There is no need to have another (ifndeffed) definition of CMSPAR. It's
defined in includes.
Signed-off-by: Jiri Slaby <jirislaby@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/char/mxser_new.c | 4 ----
1 files changed, 4 deletions(-)
diff -puN drivers/char/mxser_new.c~char-mxser_new-cmspar-is-defined drivers/char/mxser_new.c
--- a/drivers/char/mxser_new.c~char-mxser_new-cmspar-is-defined
+++ a/drivers/char/mxser_new.c
@@ -1602,10 +1602,6 @@ static int mxser_read_register(int port,
return id;
}
-#ifndef CMSPAR
-#define CMSPAR 010000000000
-#endif
-
static int mxser_ioctl_special(unsigned int cmd, void __user *argp)
{
struct mxser_port *port;
_
Patches currently in -mm which might be from jirislaby@xxxxxxxxx are
origin.patch
git-watchdog.patch
char-kill-unneeded-memsets.patch
char-serial167-remove-useless-tty-check.patch
pci-mxser-pci-refcounts.patch
mxser-make-an-experimental-clone.patch
char-mxser_new-correct-include-file.patch
char-mxser_new-upgrade-to-191.patch
char-mxser_new-rework-to-allow-dynamic-structs.patch
char-mxser_new-use-__devinit-macros.patch
char-mxser_new-pci_request_region-for-pci-regions.patch
char-mxser_new-check-request_region-retvals.patch
char-mxser_new-kill-unneeded-memsets.patch
char-mxser_new-revert-spin_lock-changes.patch
char-mxser_new-remove-request-for-testers-line.patch
char-mxser_new-debug-printk-dependent-on-debug.patch
char-mxser_new-alter-license-terms.patch
char-mxser_new-code-upside-down.patch
char-mxser_new-cmspar-is-defined.patch
hisax-niccy-cleanup.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
