From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki " <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Borislav Petkov <bp@suse.de>,
intel-gfx@lists.freedesktop.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 3/5] ACPI / bus: Switch to use new generic UUID API
Date: Wed, 31 May 2017 22:41:50 +0300 [thread overview]
Message-ID: <20170531194152.65927-4-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20170531194152.65927-1-andriy.shevchenko@linux.intel.com>
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.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/acpi/bus.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index 784bda663d16..042cd16265b3 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -225,13 +225,13 @@ acpi_status acpi_run_osc(acpi_handle handle, struct acpi_osc_context *context)
struct acpi_object_list input;
union acpi_object in_params[4];
union acpi_object *out_obj;
- u8 uuid[16];
+ guid_t guid;
u32 errors;
struct acpi_buffer output = {ACPI_ALLOCATE_BUFFER, NULL};
if (!context)
return AE_ERROR;
- if (ACPI_FAILURE(acpi_str_to_uuid(context->uuid_str, uuid)))
+ if (guid_parse(context->uuid_str, &guid))
return AE_ERROR;
context->ret.length = ACPI_ALLOCATE_BUFFER;
context->ret.pointer = NULL;
@@ -241,7 +241,7 @@ acpi_status acpi_run_osc(acpi_handle handle, struct acpi_osc_context *context)
input.pointer = in_params;
in_params[0].type = ACPI_TYPE_BUFFER;
in_params[0].buffer.length = 16;
- in_params[0].buffer.pointer = uuid;
+ in_params[0].buffer.pointer = (u8 *)&guid;
in_params[1].type = ACPI_TYPE_INTEGER;
in_params[1].integer.value = context->rev;
in_params[2].type = ACPI_TYPE_INTEGER;
--
2.11.0
next prev parent reply other threads:[~2017-05-31 19:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:41 [PATCH v2 0/5] ACPI et al: convert to use new UUID API Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 1/5] acpi, nfit: Switch to use new generic " Andy Shevchenko
2017-06-01 14:26 ` Dan Williams
2017-06-05 16:01 ` Christoph Hellwig
2017-06-05 16:18 ` Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 2/5] ACPI / APEI: " Andy Shevchenko
2017-05-31 23:56 ` kbuild test robot
2017-06-01 9:50 ` Andy Shevchenko
2017-06-05 16:01 ` Christoph Hellwig
2017-06-05 16:19 ` Andy Shevchenko
2017-06-05 16:22 ` Christoph Hellwig
2017-06-05 16:28 ` Andy Shevchenko
2017-05-31 19:41 ` Andy Shevchenko [this message]
2017-05-31 22:42 ` [PATCH v2 3/5] ACPI / bus: " Rafael J. Wysocki
2017-05-31 23:56 ` kbuild test robot
2017-06-01 0:05 ` kbuild test robot
2017-06-05 16:03 ` Christoph Hellwig
2017-06-05 16:20 ` Andy Shevchenko
2017-06-05 20:37 ` Rafael J. Wysocki
2017-06-06 9:58 ` Christoph Hellwig
2017-05-31 19:41 ` [PATCH v2 4/5] ACPI / extlog: " Andy Shevchenko
2017-06-05 16:06 ` Christoph Hellwig
2017-06-05 16:23 ` Andy Shevchenko
2017-06-05 21:23 ` Christoph Hellwig
2017-05-31 19:41 ` [PATCH v2 5/5] ACPI: Switch to use generic guid_t in acpi_evaluate_dsm() Andy Shevchenko
2017-05-31 20:21 ` Mark Brown
2017-05-31 22:42 ` Rafael J. Wysocki
2017-06-01 6:03 ` Christoph Hellwig
2017-06-01 0:08 ` kbuild test robot
2017-06-01 0:11 ` kbuild test robot
2017-06-01 14:12 ` Jarkko Sakkinen
2017-06-01 14:24 ` Dan Williams
2017-06-02 12:25 ` Adrian Hunter
2017-05-31 19:45 ` [PATCH v2 0/5] ACPI et al: convert to use new UUID API Christoph Hellwig
2017-05-31 19:45 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-05-31 20:07 ` [PATCH v2 0/5] " 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=20170531194152.65927-4-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).