From: Alexey Starikovskiy <aystarik@gmail.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: [PATCH 1/3] Add a generic API for _OSC
Date: Wed, 28 Oct 2009 11:02:12 +0300 [thread overview]
Message-ID: <4AE7FA84.1020203@gmail.com> (raw)
In-Reply-To: <20091028021930.GA31320@sli10-desk.sh.intel.com>
Shaohua Li пишет:
> On Tue, Oct 27, 2009 at 11:52:45PM +0800, Alexey Starikovskiy wrote:
>
>> Hi Shaohua,
>>
>> Could you also make it take a spec string as argument, not a prepared
>> byte buffer?
>>
> Hi,
> did you mean take the uuid string as an argument of the API? We can
> add a function to convert a uuid string to binary, but I didn't see
> any benefit to take the string as argument.
>
> Thanks,
> Shaohua
>
Hi,
Well, right now you are programming in machine codes. If you make
mistake, no one will notice, even yourself.
Programming languages were invented to make programs look more readable
by humans, so that they can see mistakes more easily.
For the same reason ACPI specification declares UUIDs as strings, while
having them in AML as byte arrays.
Function to convert UUID to byte array already exists, you just need to
use it...
Regards,
Alex.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-28 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 6:36 [PATCH 1/3] Add a generic API for _OSC Shaohua Li
2009-10-27 7:59 ` Kenji Kaneshige
2009-10-27 15:07 ` Bjorn Helgaas
2009-10-28 3:02 ` Kenji Kaneshige
2009-10-27 15:52 ` Alexey Starikovskiy
2009-10-28 2:19 ` Shaohua Li
2009-10-28 8:02 ` Alexey Starikovskiy [this message]
2009-10-28 8:47 ` Shaohua Li
2009-10-28 10:54 ` Alexey Starikovskiy
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=4AE7FA84.1020203@gmail.com \
--to=aystarik@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=shaohua.li@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