From: akpm@linux-foundation.org
To: jirislaby@gmail.com, alan@redhat.com, mm-commits@vger.kernel.org
Subject: - char-mxser-0-to-null-in-pointer.patch removed from -mm tree
Date: Fri, 08 Feb 2008 00:09:56 -0800 [thread overview]
Message-ID: <200802080809.m1889bBA014849@imap1.linux-foundation.org> (raw)
The patch titled
Char: mxser, 0 to NULL in pointer
has been removed from the -mm tree. Its filename was
char-mxser-0-to-null-in-pointer.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: Char: mxser, 0 to NULL in pointer
From: Jiri Slaby <jirislaby@gmail.com>
Don't test a pointer against 0. Use NULL instead.
Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
Reviewed-by: Alan Cox <alan@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/char/mxser_new.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/char/mxser_new.c~char-mxser-0-to-null-in-pointer drivers/char/mxser_new.c
--- a/drivers/char/mxser_new.c~char-mxser-0-to-null-in-pointer
+++ a/drivers/char/mxser_new.c
@@ -2153,7 +2153,7 @@ static void mxser_transmit_chars(struct
return;
}
- if (port->xmit_buf == 0)
+ if (port->xmit_buf == NULL)
return;
if ((port->xmit_cnt <= 0) || port->tty->stopped ||
_
Patches currently in -mm which might be from jirislaby@gmail.com are
origin.patch
git-drm.patch
drm-i915-fix-oops-after-killing-x.patch
git-watchdog.patch
moxa-first-pass-at-termios-reporting.patch
char-applicom-use-pci_resource_start.patch
char-applicom-use-pci_match_id.patch
char-applicom-use-pci_match_id-fix.patch
reiser4.patch
shrink_slab-handle-bad-shrinkers.patch
reply other threads:[~2008-02-08 8:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802080809.m1889bBA014849@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.