From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: David Weinehall <tao@acc.umu.se>
Cc: vda@port.imtp.ilyichevsk.odessa.ua, Ren <l.s.r@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Inline vfat_strnicmp()
Date: Fri, 01 Aug 2003 00:00:36 +0900 [thread overview]
Message-ID: <874r12yc4r.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20030731140442.GE16315@khan.acc.umu.se>
David Weinehall <tao@acc.umu.se> writes:
> And how big is the performance loss? Is it even measurable?
> And even if it is, is optimizing this really worth the trouble?
48bytes smaller than prev. I think It's not a clear reason for
rejecting a patch.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2003-07-31 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 15:21 [PATCH] Inline vfat_strnicmp() Ren
2003-07-27 16:33 ` OGAWA Hirofumi
2003-07-31 12:33 ` Denis Vlasenko
2003-07-31 13:52 ` OGAWA Hirofumi
2003-07-31 14:04 ` David Weinehall
2003-07-31 15:00 ` OGAWA Hirofumi [this message]
2003-07-31 14:06 ` Denis Vlasenko
2003-07-31 15:07 ` OGAWA Hirofumi
2003-08-01 5:55 ` Denis Vlasenko
2003-08-01 15:47 ` OGAWA Hirofumi
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=874r12yc4r.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=l.s.r@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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).