From: Christoph Hellwig <hch@lst.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Christoph Hellwig <hch@lst.de>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] thermal: int340x_thermal: Switch to use new generic UUID API
Date: Fri, 9 Jun 2017 15:18:54 +0200 [thread overview]
Message-ID: <20170609131854.GA20026@lst.de> (raw)
In-Reply-To: <20170609083306.83431-1-andriy.shevchenko@linux.intel.com>
On Fri, Jun 09, 2017 at 11:33:06AM +0300, Andy Shevchenko wrote:
> There are new types and helpers that are supposed to be used in
> new code.
>
> As a preparation to get rid of legacy types and API functions do
> the conversion here.
>
> The conversion fixes a potential bug in int340x_thermal as well
> since we have to use memcmp() on binary data.
Thanks Andy, applied.
prev parent reply other threads:[~2017-06-09 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 8:33 [PATCH v1] thermal: int340x_thermal: Switch to use new generic UUID API Andy Shevchenko
2017-06-09 13:18 ` Christoph Hellwig [this message]
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=20170609131854.GA20026@lst.de \
--to=hch@lst.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).