From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
George Spelvin <linux@sciencehorizons.net>
Cc: bbjorn@mork.no, linux-kernel@vger.kernel.org, tytso@mit.edu,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH] lib/uuid.c: eliminate uuid_[bl]e_index arrays
Date: Wed, 01 Jun 2016 23:13:32 +0300 [thread overview]
Message-ID: <1464812012.1767.12.camel@linux.intel.com> (raw)
In-Reply-To: <20160601125828.27b12b560802a23c63a02b15@linux-foundation.org>
On Wed, 2016-06-01 at 12:58 -0700, Andrew Morton wrote:
> On 31 May 2016 16:31:22 -0400 "George Spelvin" <linux@sciencehorizons.
> net> wrote:
>
> > This patch is on top of the upper/lower case hex optimization for
> > lib/vsprintf.c I sent earlier.
>
> I can't find it. Please take more care when referring to patches, to
> prevent mistakes from being made.
In any case I would to hear from people before going with them. Rasmus,
perhaps you can comment on the subject?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-06-01 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464594339.27624.45.camel@linux.intel.com>
2016-05-30 17:32 ` [PATCH] lib/vsprintf.c: Further simplify uuid_string() George Spelvin
2016-05-31 20:31 ` [PATCH] lib/uuid.c: eliminate uuid_[bl]e_index arrays George Spelvin
2016-05-31 21:36 ` Joe Perches
2016-05-31 22:05 ` George Spelvin
2016-06-01 12:32 ` Andy Shevchenko
2016-06-01 15:07 ` George Spelvin
2016-06-02 16:48 ` Joe Perches
2016-06-01 19:58 ` Andrew Morton
2016-06-01 20:13 ` Andy Shevchenko [this message]
2016-06-03 11:17 ` Andy Shevchenko
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=1464812012.1767.12.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bbjorn@mork.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@sciencehorizons.net \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.