linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Tai <thomas.tai@oracle.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, Tyler Baicar <tbaicar@codeaurora.org>
Subject: Re: [PATCH v1] ras: Use consistent types for UUIDs
Date: Thu, 24 Jan 2019 16:15:49 -0500	[thread overview]
Message-ID: <55579a78-85d3-ff03-86a8-79021230f141@oracle.com> (raw)
In-Reply-To: <20190109160759.GI9170@smile.fi.intel.com>



On 1/9/19 11:07 AM, Andy Shevchenko wrote:
> On Fri, Oct 05, 2018 at 09:33:05AM +0200, Christoph Hellwig wrote:
>> On Fri, Jul 13, 2018 at 04:10:27PM +0300, Andy Shevchenko wrote:
>>> The commit
>>>
>>>    297b64c74385 ("ras: acpi / apei: generate trace event for unrecognized CPER section")
>>>
>>> brought inconsistency in UUID types which are used across the RAS subsystem.
>>>
>>> Fix this by moving to use guid_t everywhere.
>>
>> Looks good,
>>
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> Thanks, Christoph.
> 
> Tomas, Tyler, any comments from your side?

Thanks for asking. I have no comments on my side.

Thanks,
Thomas

> I can push it through my tree if it looks abandon, or if Christoph is okay
> through UUID one.
> 

  reply	other threads:[~2019-01-24 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 13:10 [PATCH v1] ras: Use consistent types for UUIDs Andy Shevchenko
2018-10-03 17:26 ` Andy Shevchenko
2018-10-05  7:33 ` Christoph Hellwig
2019-01-09 16:07   ` Andy Shevchenko
2019-01-24 21:15     ` Thomas Tai [this message]
2019-01-24 20:57   ` Andy Shevchenko
2019-01-24 21:25     ` Borislav Petkov

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=55579a78-85d3-ff03-86a8-79021230f141@oracle.com \
    --to=thomas.tai@oracle.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tbaicar@codeaurora.org \
    /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).