From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Lutomirski <luto@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] platform/x86: wmi: Switch to use new generic UUID API
Date: Sun, 13 Aug 2017 17:15:55 +0300 [thread overview]
Message-ID: <1502633755.15214.4.camel@linux.intel.com> (raw)
In-Reply-To: <CALCETrVUctPyYNjkLL3uZUdxFko9=tpMchpV09VpWEhbjMT16g@mail.gmail.com>
On Sun, 2017-08-06 at 08:43 -0700, Andy Lutomirski wrote:
> On Fri, Aug 4, 2017 at 8:27 AM, Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Fri, Aug 4, 2017 at 6:01 PM, Andy Lutomirski <luto@kernel.org>
> > wrote:
> > > > On Aug 2, 2017, at 9:28 AM, Andy Shevchenko <andriy.shevchenko@l
> > > > inux.intel.com> wrote:
> > > NAK. guid_block is a firmware interface, so opaque kernel types
> > > don't
> > > belong in it.
> >
> > I f we leave this, what do you think about everything else?
>
> Assuming it works, it's fine with me. I'd be happy to test.
Just sent v2.
> Keep in mind that this beast is a *little-endian* GUID abomination,
> and I don't see generic conversion helpers. Something might need to
> be added.
Do you mean something like char16_to_guid() / char16_to_uuid() ?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-08-13 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 13:28 [PATCH v1] platform/x86: wmi: Switch to use new generic UUID API Andy Shevchenko
2017-08-04 15:01 ` Andy Lutomirski
2017-08-04 15:27 ` Andy Shevchenko
2017-08-06 15:43 ` Andy Lutomirski
2017-08-13 14:15 ` Andy Shevchenko [this message]
2017-08-13 15:23 ` Andy Lutomirski
2017-08-13 15:34 ` Andy Lutomirski
2017-08-30 12:25 ` Christoph Hellwig
2017-08-30 20:01 ` Andy Lutomirski
2017-09-01 8:23 ` Christoph Hellwig
2017-09-01 15:36 ` Andy Lutomirski
-- strict thread matches above, loose matches on Subject: below --
2018-07-13 12:53 Andy Shevchenko
2018-07-13 13:08 ` 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=1502633755.15214.4.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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.