From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2o: use kstrdup()
Date: Sat, 6 Aug 2011 11:14:30 +0100 [thread overview]
Message-ID: <20110806111430.5ae2ca0d@pyx> (raw)
In-Reply-To: <1312623053.5589.67.camel@localhost.localdomain>
On Sat, 06 Aug 2011 11:30:50 +0200
Thomas Meyer <thomas@m3y3r.de> wrote:
> From: Thomas Meyer <thomas@m3y3r.de>
>
> Use kstrdup rather than duplicating its implementation
>
> The semantic patch that makes this output is available
> in scripts/coccinelle/api/kstrdup.cocci.
>
> More information about semantic patching is available at
> http://coccinelle.lip6.fr/
>
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
Acked-by: Alan Cox <alan@linux.intel.com>
prev parent reply other threads:[~2011-08-06 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 9:30 [PATCH] i2o: use kstrdup() Thomas Meyer
2011-08-06 10:14 ` Alan Cox [this message]
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=20110806111430.5ae2ca0d@pyx \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox