From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Joe Perches <joe@perches.com>,
George Spelvin <linux@sciencehorizons.net>
Cc: bjorn@mork.no, linux-kernel@vger.kernel.org,
matt@codeblueprint.co.uk, rv@rasmusvillemoes.dk,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, devel@acpica.org
Subject: Re: [PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays
Date: Sun, 05 Jun 2016 19:15:55 +0300 [thread overview]
Message-ID: <1465143355.1767.87.camel@linux.intel.com> (raw)
In-Reply-To: <1465140873.11800.59.camel@perches.com>
On Sun, 2016-06-05 at 08:34 -0700, Joe Perches wrote:
> On Sun, 2016-06-05 at 17:19 +0300, Andy Shevchenko wrote:
> > On Sat, 2016-06-04 at 09:29 -0700, Joe Perches wrote:
> > > (adding acpi folks)
> > > Trivially, acpi defines this but doesn't seem to use it.
> > >
> > > include/acpi/acconfig.h:#define UUID_STRING_LENGTH 36 /*
> > > Total length of a UUID string */
> > >
> > > And Ingo commented last month:
> > > https://lkml.org/lkml/2016/4/29/69
> > >
> > > Maybe this __uuid_to_bin function should be made public and
> > > the acpi version in drivers/acpi/acpica/utuuid.c should be
> > > removed.
> > Looks like you missed my first version of (other) series.
> > http://www.spinics.net/lists/linux-api/msg17518.html
>
> More like if a patch isn't applied after several months,
> it's likely not going to be applied unless it is resent.
The discussion was about how to proceed with uuid_*_cmp() functions that
have prototypes like uuid_le x1, x2. Any ideas come to mind?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Joe Perches <joe@perches.com>,
George Spelvin <linux@sciencehorizons.net>
Cc: bjorn@mork.no, linux-kernel@vger.kernel.org,
matt@codeblueprint.co.uk, rv@rasmusvillemoes.dk,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, devel@acpica.org
Subject: Re: [PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays
Date: Sun, 05 Jun 2016 19:15:55 +0300 [thread overview]
Message-ID: <1465143355.1767.87.camel@linux.intel.com> (raw)
In-Reply-To: <1465140873.11800.59.camel@perches.com>
On Sun, 2016-06-05 at 08:34 -0700, Joe Perches wrote:
> On Sun, 2016-06-05 at 17:19 +0300, Andy Shevchenko wrote:
> > On Sat, 2016-06-04 at 09:29 -0700, Joe Perches wrote:
> > > (adding acpi folks)
> > > Trivially, acpi defines this but doesn't seem to use it.
> > >
> > > include/acpi/acconfig.h:#define UUID_STRING_LENGTH 36 /*
> > > Total length of a UUID string */
> > >
> > > And Ingo commented last month:
> > > https://lkml.org/lkml/2016/4/29/69
> > >
> > > Maybe this __uuid_to_bin function should be made public and
> > > the acpi version in drivers/acpi/acpica/utuuid.c should be
> > > removed.
> > Looks like you missed my first version of (other) series.
> > http://www.spinics.net/lists/linux-api/msg17518.html
>
> More like if a patch isn't applied after several months,
> it's likely not going to be applied unless it is resent.
The discussion was about how to proceed with uuid_*_cmp() functions that
have prototypes like uuid_le x1, x2. Any ideas come to mind?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-06-05 16:14 UTC|newest]
Thread overview: 20+ 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 14:19 ` Andy Shevchenko
2016-06-05 15:34 ` Joe Perches
2016-06-05 15:34 ` Joe Perches
2016-06-05 16:15 ` Andy Shevchenko [this message]
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
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=1465143355.1767.87.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bjorn@mork.no \
--cc=devel@acpica.org \
--cc=joe@perches.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sciencehorizons.net \
--cc=lv.zheng@intel.com \
--cc=matt@codeblueprint.co.uk \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--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 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.