From: "hch@lst.de" <hch@lst.de>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "hch@lst.de" <hch@lst.de>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>, "bp@suse.de" <bp@suse.de>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] acpi, nfit: Switch to use new generic UUID API
Date: Wed, 7 Jun 2017 12:19:55 +0200 [thread overview]
Message-ID: <20170607101955.GA29052@lst.de> (raw)
In-Reply-To: <1496816744.6978.6.camel@intel.com>
On Wed, Jun 07, 2017 at 06:25:46AM +0000, Williams, Dan J wrote:
> With one compile fix below the 'acpi' branch works for me. Please feel
> free to add:
The mail seems to contain garbage that can't be applied, but I just
applied the changes manually.
next prev parent reply other threads:[~2017-06-07 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 16:40 [PATCH v3 0/5] ACPI et al: convert to use new UUID API Andy Shevchenko
2017-06-05 16:40 ` [PATCH v3 1/5] acpi, nfit: Switch to use new generic " Andy Shevchenko
2017-06-05 16:49 ` Dan Williams
2017-06-05 17:10 ` Andy Shevchenko
2017-06-05 21:22 ` Christoph Hellwig
2017-06-07 6:25 ` Williams, Dan J
2017-06-07 9:37 ` Andy Shevchenko
2017-06-07 10:17 ` hch
2017-06-07 10:19 ` hch [this message]
2017-06-05 16:40 ` [PATCH v3 2/5] ACPI / APEI: " Andy Shevchenko
2017-06-05 16:40 ` [PATCH v3 3/5] ACPI / bus: " Andy Shevchenko
2017-06-05 16:40 ` [PATCH v3 4/5] ACPI / extlog: " Andy Shevchenko
2017-06-05 16:40 ` [PATCH v3 5/5] ACPI: Switch to use generic guid_t in acpi_evaluate_dsm() 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=20170607101955.GA29052@lst.de \
--to=hch@lst.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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