From: Jiri Slaby <jirislaby@gmail.com>
To: Julia Lawall <julia@diku.dk>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 5/5, revised] staging/otus: Drop an unnecessary NULL test
Date: Sat, 11 Jul 2009 08:33:38 +0000 [thread overview]
Message-ID: <4A584E62.6050500@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0907111031480.29592@ask.diku.dk>
On 07/11/2009 10:32 AM, Julia Lawall wrote:
> Apparently, the NULL test is not necessary at this point.
>
> The semantic patch that finds this problem is as follows:
> (http://www.emn.fr/x-info/coccinelle/)
...
> Signed-off-by: Julia Lawall <julia@diku.dk>
Acked-by: Jiri Slaby <jirislaby@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: Julia Lawall <julia@diku.dk>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 5/5, revised] staging/otus: Drop an unnecessary NULL test
Date: Sat, 11 Jul 2009 10:33:38 +0200 [thread overview]
Message-ID: <4A584E62.6050500@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0907111031480.29592@ask.diku.dk>
On 07/11/2009 10:32 AM, Julia Lawall wrote:
> Apparently, the NULL test is not necessary at this point.
>
> The semantic patch that finds this problem is as follows:
> (http://www.emn.fr/x-info/coccinelle/)
...
> Signed-off-by: Julia Lawall <julia@diku.dk>
Acked-by: Jiri Slaby <jirislaby@gmail.com>
next prev parent reply other threads:[~2009-07-11 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 8:32 [PATCH 5/5, revised] staging/otus: Drop an unnecessary NULL test Julia Lawall
2009-07-11 8:32 ` Julia Lawall
2009-07-11 8:33 ` Jiri Slaby [this message]
2009-07-11 8:33 ` Jiri Slaby
2009-07-11 17:04 ` [PATCH 5/5, revised] staging/otus: Drop an unnecessary NULL Greg KH
2009-07-11 17:04 ` [PATCH 5/5, revised] staging/otus: Drop an unnecessary NULL test Greg KH
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=4A584E62.6050500@gmail.com \
--to=jirislaby@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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.