From: Hans de Goede <hdegoede@redhat.com>
To: Pavel Machek <pavel@ucw.cz>, Jorge Lopez <jorgealtxwork@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas@t-8ch.de
Subject: Re: [PATCH v10 02/14] HP BIOSCFG driver - biosattr-interface
Date: Tue, 25 Apr 2023 12:30:59 +0200 [thread overview]
Message-ID: <6ddd373b-6bcb-85a7-2423-ceea5d3f1246@redhat.com> (raw)
In-Reply-To: <ZEJ1f7vOL1zCyNyR@duo.ucw.cz>
Hi,
On 4/21/23 13:37, Pavel Machek wrote:
> Hi!
>
>> Linux Security components are under development and not published yet.
>> The only linux component is the driver (hp bioscfg) at this time.
>> Other published security components are under Windows.
>>
>> Signed-off-by: Jorge Lopez <jorge.lopez2@hp.com>
>
>> +/*
>> + * ascii_to_utf16_unicode - Convert ascii string to UTF-16 unicode
>> + *
>> + * BIOS supports UTF-16 characters that are 2 bytes long. No variable
>> + * multi-byte language supported.
>> + *
>> + * @p: Unicode buffer address
>> + * @str: string to convert to unicode
>> + *
>> + * Returns a void pointer to the buffer containing unicode string
>> + */
>> +void *ascii_to_utf16_unicode(u16 *p, const u8 *str)
>> +{
>
> Does this need to go to library somewhere?
This has already been discussed in earlier submissions
of the driver, the utf16 format is HP specific (prefixed
with a 16 bit le lenght, and the 0 length string needs
special encoding) so despite the name this is not generic.
It should probably be prefixed with hp_ because of this
though, to avoid potential symbol conflicts when builtin.
(and the same applies to other generic functions).
Regards,
Hans
next prev parent reply other threads:[~2023-04-25 10:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 15:13 [PATCH v10 00/14] HP BIOSCFG driver Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 01/14] HP BIOSCFG driver - Documentation Jorge Lopez
2023-04-21 11:36 ` Pavel Machek
2023-04-19 15:13 ` [PATCH v10 02/14] HP BIOSCFG driver - biosattr-interface Jorge Lopez
2023-04-21 11:37 ` Pavel Machek
2023-04-25 10:30 ` Hans de Goede [this message]
2023-04-25 13:43 ` Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 03/14] HP BIOSCFG driver - bioscfg Jorge Lopez
2023-04-19 18:04 ` Armin Wolf
2023-04-19 20:59 ` Limonciello, Mario
2023-04-25 10:34 ` Hans de Goede
2023-04-25 14:32 ` Jorge Lopez
2023-04-25 14:59 ` Hans de Goede
2023-04-25 18:47 ` Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 04/14] HP BIOSCFG driver - int-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 05/14] HP BIOSCFG driver - ordered-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 06/14] HP BIOSCFG driver - passwdobj-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 07/14] HP BIOSCFG driver - string-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 08/14] HP BIOSCFG driver - bioscfg-h Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 09/14] HP BIOSCFG driver - enum-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 10/14] HP BIOSCFG driver - passwdattr-interface Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 11/14] HP BIOSCFG driver - spmobj-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 12/14] HP BIOSCFG driver - surestart-attributes Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 13/14] HP BIOSCFG driver - Makefile Jorge Lopez
2023-04-20 1:44 ` kernel test robot
2023-04-20 13:33 ` Jorge Lopez
2023-04-20 3:57 ` kernel test robot
2023-04-20 13:28 ` Jorge Lopez
2023-04-19 15:13 ` [PATCH v10 14/14] HP BIOSCFG driver - MAINTAINERS Jorge Lopez
-- strict thread matches above, loose matches on Subject: below --
2023-04-19 15:12 [PATCH v10 00/14] HP BIOSCFG driver Jorge Lopez
2023-04-19 15:12 ` [PATCH v10 02/14] HP BIOSCFG driver - biosattr-interface Jorge Lopez
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=6ddd373b-6bcb-85a7-2423-ceea5d3f1246@redhat.com \
--to=hdegoede@redhat.com \
--cc=jorgealtxwork@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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
all inboxes | Powered by JetHome®