The patch titled
Char: serial167, remove useless tty check
has been added to the -mm tree. Its filename is
char-serial167-remove-useless-tty-check.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: serial167, remove useless tty check
From: Jiri Slaby <jirislaby@xxxxxxxxx>
serial167, remove useless tty check
tty is dereferenced before it is checked to be non-NULL. Remove such
check.
Signed-off-by: Jiri Slaby <jirislaby@xxxxxxxxx>
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/char/serial167.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN drivers/char/serial167.c~char-serial167-remove-useless-tty-check drivers/char/serial167.c
--- a/drivers/char/serial167.c~char-serial167-remove-useless-tty-check
+++ a/drivers/char/serial167.c
@@ -1121,7 +1121,7 @@ cy_put_char(struct tty_struct *tty, unsi
if (serial_paranoia_check(info, tty->name, "cy_put_char"))
return;
- if (!tty || !info->xmit_buf)
+ if (!info->xmit_buf)
return;
local_irq_save(flags);
@@ -1187,7 +1187,7 @@ cy_write(struct tty_struct * tty,
return 0;
}
- if (!tty || !info->xmit_buf){
+ if (!info->xmit_buf){
return 0;
}
_
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
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
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
