From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
Christoph Hellwig <hch@lst.de>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: linux-next: manual merge of the usb tree with the uuid tree
Date: Thu, 29 Jun 2017 17:59:13 +0300 [thread overview]
Message-ID: <1498748353.22624.231.camel@linux.intel.com> (raw)
In-Reply-To: <20170629144844.3214d21e@canb.auug.org.au>
On Thu, 2017-06-29 at 14:48 +1000, Stephen Rothwell wrote:
> I got the following error:
>
> drivers/usb/typec/ucsi/ucsi_acpi.c: In function 'ucsi_acpi_dsm':
> drivers/usb/typec/ucsi/ucsi_acpi.c:33:48: error: passing argument 2 of
> 'acpi_evaluate_dsm' from incompatible pointer type [-
> Werror=incompatible-pointer-types]
> obj = acpi_evaluate_dsm(ACPI_HANDLE(ua->dev), ua->uuid.b, 1, func,
> ^
> In file included from include/linux/acpi.h:44:0,
> from drivers/usb/typec/ucsi/ucsi_acpi.c:14:
> include/acpi/acpi_bus.h:65:20: note: expected 'const guid_t * {aka
> const struct <anonymous> *}' but argument is of type '__u8 * {aka
> unsigned char *}'
> union acpi_object *acpi_evaluate_dsm(acpi_handle handle, const guid_t
> *guid,
> ^
>
> I have applied the following merge fix patch (the first hunk is
> probably not strictly necessary):
It is necessary. The goal of next portion of the UUID related stuff is
to get rid of those _le / _be types completely (uuid_be gone I suppose
already).
Patch itself looks good to me.
> - uuid_le uuid;
> + guid_t uuid;
> };
>
> static int ucsi_acpi_dsm(struct ucsi_acpi *ua, int func)
> {
> union acpi_object *obj;
>
> - obj = acpi_evaluate_dsm(ACPI_HANDLE(ua->dev), ua->uuid.b, 1,
> func,
> + obj = acpi_evaluate_dsm(ACPI_HANDLE(ua->dev), &ua->uuid, 1,
> func,
> NULL);
Can it be one line after all?
> if (!obj) {
> dev_err(ua->dev, "%s: failed to evaluate _DSM %d\n",
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-06-29 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 4:48 linux-next: manual merge of the usb tree with the uuid tree Stephen Rothwell
2017-06-29 14:59 ` Andy Shevchenko [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=1498748353.22624.231.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=heikki.krogerus@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).