From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, "Theodore Ts'o" <tytso@mit.edu>,
Matt Fleming <matt@codeblueprint.co.uk>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v2 0/8] uuid: convert users to generic UUID API
Date: Tue, 05 Apr 2016 14:07:27 +0300 [thread overview]
Message-ID: <1459854447.12843.13.camel@linux.intel.com> (raw)
In-Reply-To: <20160404164020.9a3529e6e247aac6ec114fff@linux-foundation.org>
On Mon, 2016-04-04 at 16:40 -0700, Andrew Morton wrote:
> On Mon, 4 Apr 2016 16:30:02 +0300 Andy Shevchenko <andriy.shevchenko
> @linux.intel.com> wrote:
>
> >
> > There are few functions here and there along with type definitions
> > that provide
> > UUID API. This series consolidates everything under one hood and
> > converts
> > current users.
> Well. It converts two current users.
>
> There are many references to "uuid" in the tree. How many sites
> could
> potentially benefit from this change?
The big chunk is ACPI [1] though Rafael pointed out to some type
dereferencing he didn't get [2]. (By the way there is already use of
such in ACPI code from 2010: drivers/acpi/apei/ghes.c). That's why I
postponed that change.
[1] http://www.spinics.net/lists/linux-acpi/msg63811.html
[2] http://www.spinics.net/lists/linux-acpi/msg63854.html
>
> >
> > This has been tested for a while internally, however it doesn't
> > mean we covered
> > all possible cases (especially accuracy of UUID constants after
> > conversion).
> > So, please test this as much as you can and provide your tag. We
> > appreciate the
> > effort.
> I'm not sure who this series was aimed at but I saw "lib" and grabbed
> it. I'll await Matt's ack.
Yes, this is lib/ stuff, I hope the rest would provide Ack.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-04-05 11:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 13:30 [PATCH v2 0/8] uuid: convert users to generic UUID API Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 1/8] lib/vsprintf: simplify UUID printing Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 2/8] lib/uuid: move generate_random_uuid() to uuid.c Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 3/8] lib/uuid: introduce few more generic helpers for UUID Andy Shevchenko
2016-04-04 23:40 ` Andrew Morton
2016-04-04 23:55 ` Joe Perches
2016-04-05 0:48 ` Stephen Rothwell
2016-04-05 10:51 ` Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 4/8] lib/uuid: remove FSF address Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 5/8] sysctl: drop away useless label Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 6/8] sysctl: use generic UUID library Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 7/8] efi: redefine type, constant, macro from generic code Andy Shevchenko
2016-04-04 13:30 ` [PATCH v2 8/8] efivars: use generic UUID library Andy Shevchenko
2016-04-04 23:40 ` [PATCH v2 0/8] uuid: convert users to generic UUID API Andrew Morton
2016-04-05 11:07 ` Andy Shevchenko [this message]
2016-04-05 14:06 ` Matt Fleming
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=1459854447.12843.13.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=matt@codeblueprint.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox