From: Maximilian Luz <luzmaximilian@gmail.com>
To: "Schmauss, Erik" <erik.schmauss@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: Tue, 23 Jul 2019 13:38:31 +0200 [thread overview]
Message-ID: <5a6f7a66-035c-eab0-6cdf-e10411e30cef@gmail.com> (raw)
In-Reply-To: <CF6A88132359CE47947DB4C6E1709ED53C614AA8@ORSMSX122.amr.corp.intel.com>
On 7/23/19 1:01 AM, Schmauss, Erik wrote:
> Sorry about the late response. This slipped through the cracks.
> I've sent them an email just now and I'll keep you informed
No worries. Thank you.
Maximilian
next prev parent reply other threads:[~2019-07-23 11:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ef42aa1-196d-f3db-0e5d-2fd84c198242@gmail.com>
2019-03-14 17:19 ` [Devel] PROBLEM: Calling ObjectType on buffer field reports type integer Schmauss, Erik
2019-03-18 22:28 ` Schmauss, Erik
[not found] ` <fe4bcc1c-5c15-caa6-ce01-a5df962ff008@gmail.com>
2019-03-19 20:19 ` Schmauss, Erik
[not found] ` <51e156ec-c2ed-84be-13c0-99a213e1d4b7@gmail.com>
2019-03-22 21:28 ` Schmauss, Erik
2019-07-20 20:45 ` Maximilian Luz
2019-07-22 23:01 ` Schmauss, Erik
2019-07-22 23:01 ` [Devel] " Schmauss, Erik
2019-07-23 11:38 ` Maximilian Luz [this message]
2019-11-10 21:29 ` Maximilian Luz
2019-11-22 17:11 ` Moore, Robert
2019-11-22 17:11 ` [Devel] " Moore, Robert
2019-11-22 22:07 ` Moore, Robert
2019-11-22 22:07 ` [Devel] " Moore, Robert
2019-11-22 23:00 ` Maximilian Luz
2019-11-22 23:29 ` Schmauss, Erik
2019-11-22 23:29 ` [Devel] " Schmauss, Erik
2019-11-23 0:33 ` Maximilian Luz
2019-11-27 0:25 ` Schmauss, Erik
2019-11-27 0:25 ` [Devel] " 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
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=5a6f7a66-035c-eab0-6cdf-e10411e30cef@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=devel@acpica.org \
--cc=erik.schmauss@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.