From: Jung-uk Kim <jkim at FreeBSD.org>
To: devel@acpica.org
Subject: Re: [Devel] ACPICA version 20150818 released
Date: Tue, 25 Aug 2015 19:39:58 -0400 [thread overview]
Message-ID: <55DCFCCE.8080705@FreeBSD.org> (raw)
In-Reply-To: 94F2FBAB4432B54E8AACC7DFDE6C92E37D3405C5@ORSMSX112.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 08/25/2015 19:30, Moore, Robert wrote:
> Yes, I see the file.
>
> You don't actually need AcpiNames utility do you? It is more of an
> example utility, how to use smaller parts of ACPICA.
No, I don't need it. I just don't like to see broken stuff. ;-)
Jung-uk Kim
>> -----Original Message----- From: Jung-uk Kim
>> [mailto:jkim(a)FreeBSD.org] Sent: Tuesday, August 25, 2015 2:01 PM
>> To: Moore, Robert; acpica.org list Subject: Re: [Devel] ACPICA
>> version 20150818 released
>>
> On 08/25/2015 16:50, Moore, Robert wrote:
>>>>> Unfortunately, AcpiNames does not build because
>>>>> source/tools/acpinames/acpinames.h is wrongly included as
>>>>> AcpiNames.h in the release tarballs.
>>>>
>>>> Is this something new?
>
> Yes, 20150717 did not have this problem.
>
> Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJV3PzIAAoJEHyflib82/FG4AoH/jvpEIHHjOb5YbkZ6rbfhGnk
rlrsyGAj6tGCx7wDUsnTWSR5EmjPc/soRsUsK7GNfXHokFhUbRPQYkxr+fb+KPiQ
wo2ixaC4HZLhNelgjNE6bGUz00ZFM1JFvnmVDQXuI36wAdrb/9dDmQZrVYMoXA65
rURpy9buCeEYyqboHqePmOEPO9r3UTw7JlGoxHOd/UQM9TIfAArJWUSxpL2K1zvB
95656mHUfZYyZL+3ZT4uZiDBcDDHB3XMCoXLmONMmgUZj1j3e+weq4DgHMjRu4cM
pEOmG81e65XnTZxUInSrnDWyLi6s0w32jl7sZiTUlABBLUE1KtXuYpk48Lc9rXg=
=WjY3
-----END PGP SIGNATURE-----
next reply other threads:[~2015-08-25 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 23:39 Jung-uk Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-26 2:09 [Devel] ACPICA version 20150818 released Moore, Robert
2015-08-25 23:30 Moore, Robert
2015-08-25 21:01 Jung-uk Kim
2015-08-25 20:50 Moore, Robert
2015-08-25 19:32 Jung-uk Kim
2015-08-18 20:27 Moore, Robert
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=55DCFCCE.8080705@FreeBSD.org \
--to=devel@acpica.org \
/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.