From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Grant Likely <grant.likely@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC 2/2] lib: string: Make all calls to strnicmp into calls to strncasecmp
Date: Wed, 27 Aug 2014 11:13:16 +0200 [thread overview]
Message-ID: <87sikie1n7.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <20140827090537.GL5100@mwanda> (Dan Carpenter's message of "Wed, 27 Aug 2014 12:05:37 +0300")
On Wed, Aug 27 2014, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> On Wed, Aug 27, 2014 at 09:36:02AM +0200, Rasmus Villemoes wrote:
>> The previous patch made strnicmp into a wrapper for strncasecmp. This
>> patch makes all in-tree users of strnicmp call strncasecmp directly,
>> while still making sure that the strnicmp symbol can be used by
>> out-of-tree modules. It should be considered a temporary hack until
>> all in-tree callers have been converted.
>>
>> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
>
> Won't GCC just do the right thing without this second patch?
>
Not without LTO, I think. gcc can't really know how strnicmp is
implemented, so it has to emit a call to it.
Anyway, I was also planning on sending tree-wide patches doing
s/strnicmp/strncasecmp/, and then removing the hack from string.h, but I
first wanted to get feedback on the first patch and maybe some guidance
on how to properly deal with the module issue (e.g., does the kernel
need to export a strnicmp symbol forever?).
Rasmus
next prev parent reply other threads:[~2014-08-27 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 7:36 [PATCH/RFC 0/2] lib: string: Remove duplicated function Rasmus Villemoes
2014-08-27 7:36 ` [PATCH/RFC 1/2] " Rasmus Villemoes
2014-09-11 22:22 ` Andrew Morton
2014-09-12 9:01 ` Rasmus Villemoes
2014-09-12 9:43 ` Joe Perches
2014-09-12 18:52 ` Tejun Heo
2014-08-27 7:36 ` [PATCH/RFC 2/2] lib: string: Make all calls to strnicmp into calls to strncasecmp Rasmus Villemoes
2014-08-27 9:05 ` Dan Carpenter
2014-08-27 9:13 ` Rasmus Villemoes [this message]
2014-08-27 10:17 ` Dan Carpenter
2014-08-30 18:11 ` 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=87sikie1n7.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=grant.likely@linaro.org \
--cc=hpa@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®