From: Darren Hart <dvhart@infradead.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 17/22] thinkpad_acpi: Replace strnicmp with strncasecmp
Date: Tue, 16 Sep 2014 15:08:57 -0700 [thread overview]
Message-ID: <20140916220857.GA12780@vmdeb7> (raw)
In-Reply-To: <1410900696-6481-18-git-send-email-linux@rasmusvillemoes.dk>
On Tue, Sep 16, 2014 at 10:51:31PM +0200, Rasmus Villemoes wrote:
> The kernel used to contain two functions for length-delimited,
> case-insensitive string comparison, strnicmp with correct semantics
> and a slightly buggy strncasecmp. The latter is the POSIX name, so
> strnicmp was renamed to strncasecmp, and strnicmp made into a wrapper
> for the new strncasecmp to avoid breaking existing users.
When was this done? As of this morning I still see them as independent functions
in lib/string.c.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-09-16 22:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:51 [PATCH 00/22] treewide: Replace strnicmp with strncasecmp Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 01/22] ARM: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 02/22] block: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 03/22] netfilter: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 04/22] video: fbdev: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 05/22] cifs: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 06/22] ocfs2: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 07/22] isofs: " Rasmus Villemoes
2014-09-16 21:19 ` Jan Kara
2014-09-16 20:51 ` [PATCH 08/22] ALSA: hda - " Rasmus Villemoes
2014-09-17 5:54 ` Takashi Iwai
2014-09-16 20:51 ` [PATCH 09/22] batman-adv: " Rasmus Villemoes
2014-09-17 6:00 ` [B.A.T.M.A.N.] " Antonio Quartulli
2014-09-16 20:51 ` [PATCH 10/22] ACPI / battery: " Rasmus Villemoes
2014-09-25 23:46 ` Rafael J. Wysocki
2014-09-16 20:51 ` [PATCH 11/22] cpufreq: " Rasmus Villemoes
2014-09-16 21:22 ` Viresh Kumar
2014-09-25 23:53 ` Rafael J. Wysocki
2014-09-16 20:51 ` [PATCH 12/22] cpuidle: " Rasmus Villemoes
2014-09-25 23:52 ` Rafael J. Wysocki
2014-09-16 20:51 ` [PATCH 13/22] scsi: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 14/22] ib_srpt: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 15/22] Input: edt-ft5x06 - " Rasmus Villemoes
2014-09-17 16:26 ` Dmitry Torokhov
2014-09-16 20:51 ` [PATCH 16/22] altera-stapl: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 17/22] thinkpad_acpi: " Rasmus Villemoes
2014-09-16 22:08 ` Darren Hart [this message]
2014-09-17 8:12 ` Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 18/22] PNP: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 19/22] s390/cio: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 20/22] staging: r8188eu: " Rasmus Villemoes
2014-09-16 20:51 ` [PATCH 21/22] Thermal: " Rasmus Villemoes
2014-09-18 0:49 ` Zhang Rui
2014-09-16 20:51 ` [PATCH 22/22] kdb: " Rasmus Villemoes
2014-09-16 21:55 ` [PATCH 00/22] treewide: " Theodore Ts'o
2014-09-17 8:23 ` Rasmus Villemoes
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=20140916220857.GA12780@vmdeb7 \
--to=dvhart@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).