The patch titled
m68k/MVME167: SERIAL167 is no longer broken
has been removed from the -mm tree. Its filename is
m68k-mvme167-serial167-is-no-longer-broken.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: m68k/MVME167: SERIAL167 is no longer broken
From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
- SERIAL167 is no longer broken
- Removed some unused variables from the driver to fix compiler warnings
Signed-off-by: Kars de Jong <jongk@xxxxxxxxxxxxxx>
Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Cc: Roman Zippel <zippel@xxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/m68k/Kconfig | 2 +-
drivers/char/serial167.c | 2 --
2 files changed, 1 insertion(+), 3 deletions(-)
diff -puN arch/m68k/Kconfig~m68k-mvme167-serial167-is-no-longer-broken arch/m68k/Kconfig
--- a/arch/m68k/Kconfig~m68k-mvme167-serial167-is-no-longer-broken
+++ a/arch/m68k/Kconfig
@@ -604,7 +604,7 @@ config MVME147_SCC
config SERIAL167
bool "CD2401 support for MVME166/7 serial ports"
- depends on MVME16x && BROKEN
+ depends on MVME16x
help
This is the driver for the serial ports on the Motorola MVME166,
167, and 172 boards. Everyone using one of these boards should say
diff -puN drivers/char/serial167.c~m68k-mvme167-serial167-is-no-longer-broken drivers/char/serial167.c
--- a/drivers/char/serial167.c~m68k-mvme167-serial167-is-no-longer-broken
+++ a/drivers/char/serial167.c
@@ -1422,7 +1422,6 @@ cy_tiocmget(struct tty_struct *tty, stru
volatile unsigned char *base_addr = (u_char *)BASE_ADDR;
unsigned long flags;
unsigned char status;
- unsigned int result;
channel = info->line;
@@ -1446,7 +1445,6 @@ cy_tiocmset(struct tty_struct *tty, stru
int channel;
volatile unsigned char *base_addr = (u_char *)BASE_ADDR;
unsigned long flags;
- unsigned int arg;
channel = info->line;
_
Patches currently in -mm which might be from geert@xxxxxxxxxxxxxx are
origin.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
