From: Maximilian Luz <luzmaximilian@gmail.com>
To: "Kaneda, Erik" <erik.kaneda@intel.com>,
"Moore, Robert" <robert.moore@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: Re: PROBLEM: Calling ObjectType on buffer field reports type integer
Date: Fri, 6 Dec 2019 14:48:20 +0100 [thread overview]
Message-ID: <eee7a218-8def-df83-36d0-b4799050e10f@gmail.com> (raw)
In-Reply-To: <DM6PR11MB3612BE55D4E70040DEB102DCF05C0@DM6PR11MB3612.namprd11.prod.outlook.com>
On 12/6/19 12:57 AM, Kaneda, Erik wrote:
> Your solution looks very similar to my patch.
> In AcpiDsInitBufferField, I would prefer to use a new field "is_create_field" or something like that. AML_FIELD_ACCESS_BUFFER
> does get used in other parts of ACPICA so let's create and use a new field in the object union.
>
> Go ahead and re-submit the patch with the above changes. I'll edit your explanation with more details and include this in
> the next ACPICA release. It'll land in linux after the release.
Thank you!
I've re-submitted the patch with the requested changes and included your
comments.
Regards,
Maximilian
prev parent reply other threads:[~2019-12-06 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ef42aa1-196d-f3db-0e5d-2fd84c198242@gmail.com>
[not found] ` <CF6A88132359CE47947DB4C6E1709ED53C592D47@ORSMSX122.amr.corp.intel.com>
[not found] ` <CF6A88132359CE47947DB4C6E1709ED53C59405C@ORSMSX122.amr.corp.intel.com>
[not found] ` <fe4bcc1c-5c15-caa6-ce01-a5df962ff008@gmail.com>
[not found] ` <CF6A88132359CE47947DB4C6E1709ED53C5942CA@ORSMSX122.amr.corp.intel.com>
[not found] ` <51e156ec-c2ed-84be-13c0-99a213e1d4b7@gmail.com>
[not found] ` <CF6A88132359CE47947DB4C6E1709ED53C595C50@ORSMSX122.amr.corp.intel.com>
2019-07-20 20:45 ` PROBLEM: Calling ObjectType on buffer field reports type integer Maximilian Luz
2019-07-22 23:01 ` Schmauss, Erik
2019-07-23 11:38 ` Maximilian Luz
2019-11-10 21:29 ` Maximilian Luz
2019-11-22 17:11 ` Moore, Robert
2019-11-22 22:07 ` Moore, Robert
2019-11-22 23:00 ` Maximilian Luz
2019-11-22 23:29 ` Schmauss, Erik
2019-11-23 0:33 ` Maximilian Luz
2019-11-27 0:25 ` Schmauss, Erik
2019-12-03 22:21 ` Kaneda, Erik
2019-12-04 19:33 ` Maximilian Luz
2019-12-05 23:57 ` Kaneda, Erik
2019-12-06 13:48 ` Maximilian Luz [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=eee7a218-8def-df83-36d0-b4799050e10f@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=devel@acpica.org \
--cc=erik.kaneda@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
/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