From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: George Spelvin <linux@sciencehorizons.net>
Cc: bjorn@mork.no, linux-kernel@vger.kernel.org,
matt@codeblueprint.co.uk, rv@rasmusvillemoes.dk
Subject: Re: [PATCH v2 3/2] lib/uuid.c: Silence an unchecked return value warning
Date: Mon, 06 Jun 2016 11:24:56 +0300 [thread overview]
Message-ID: <1465201496.1767.91.camel@linux.intel.com> (raw)
In-Reply-To: <20160605192527.23210.qmail@ns.sciencehorizons.net>
On Sun, 2016-06-05 at 15:25 -0400, George Spelvin wrote:
> From andriy.shevchenko@linux.intel.com Sun Jun 05 14:19:48 2016
> X-ExtLoop1: 1
> X-IronPort-AV: E=Sophos;i="5.26,421,1459839600";
> d="scan'208";a="995605979"
> Subject: Re: [PATCH v2 3/2] lib/uuid.c: Silence an unchecked return
> value
> warning
> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> To: George Spelvin <linux@sciencehorizons.net>
> Cc: bjorn@mork.no, linux-kernel@vger.kernel.org, matt@codeblueprint.co
> .uk,
> rv@rasmusvillemoes.dk
> Date: Sun, 05 Jun 2016 17:21:04 +0300
> In-Reply-To: <20160604131622.28377.qmail@ns.sciencehorizons.net>
> References: <20160604131622.28377.qmail@ns.sciencehorizons.net>
> Organization: Intel Finland Oy
> Content-Type: text/plain; charset="UTF-8"
> X-Mailer: Evolution 3.20.2-2
> Mime-Version: 1.0
> Content-Transfer-Encoding: 8bit
^^^^ Something wrong with mail configuration?
>
> Andy Shevchenko worte:
> > On Sat, 2016-06-04 at 09:16 -0400, George Spelvin wrote:
> > Which I against of. Please, use normal hex_to_bin() calls here.
> >
> > Compiler will inline it anyway, but at least will not do second
> > check
> > for nothing.
>
> Um... huh? Neither hex_to_bin() nor hex2bin() are inline functions.
> They're declared as extern in <linux/kernel.h> and defined in
> lib/hexdump.c.
>
> One call is smaller than two calls, which is why I did that.
>
> It's also faster, as hex_to_bin() *is* inlined within hex2bin()
> (if you compile with -O).
To be sure it faster we need the measurements. Sometimes it's not
obvious.
>
> Is your request based on a false premise?
Yeah, you are right, I looked at hex2bin() which is in the same module.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-06-06 8:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464952090.1767.34.camel@linux.intel.com>
2016-06-04 5:13 ` [PATCH v2 0/2] Clean up and shrink uuid input & output George Spelvin
2016-06-04 5:14 ` [PATCH v2 1/2] lib/vsprintf.c: Simplify uuid_string() George Spelvin
2016-06-05 14:22 ` Andy Shevchenko
2016-06-05 19:57 ` George Spelvin
2016-06-04 5:14 ` [PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays George Spelvin
2016-06-04 5:42 ` kbuild test robot
2016-06-04 16:29 ` Joe Perches
2016-06-04 21:57 ` George Spelvin
2016-06-05 14:19 ` Andy Shevchenko
2016-06-05 15:34 ` Joe Perches
2016-06-05 16:15 ` Andy Shevchenko
2016-06-04 13:16 ` [PATCH v2 3/2] lib/uuid.c: Silence an unchecked return value warning George Spelvin
2016-06-05 14:21 ` Andy Shevchenko
2016-06-05 19:25 ` George Spelvin
2016-06-06 8:24 ` Andy Shevchenko [this message]
2016-06-07 16:43 ` George Spelvin
2016-06-07 17:13 ` Joe Perches
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=1465201496.1767.91.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bjorn@mork.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sciencehorizons.net \
--cc=matt@codeblueprint.co.uk \
--cc=rv@rasmusvillemoes.dk \
/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