public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH 1/1] Ext4Pkg: Move unicode collation initialization to Start()
Date: Sat, 18 Feb 2023 12:30:49 +0000	[thread overview]
Message-ID: <EF2BDE6E-B565-423C-B05C-8B9DE2231DF5@posteo.de> (raw)
In-Reply-To: <20230217201427.139581-1-pedro.falcato@gmail.com>


> On 17. Feb 2023, at 21:14, Pedro Falcato <pedro.falcato@gmail.com> wrote:
> 
> @@ -169,5 +170,20 @@ Ext4StrCmpInsensitive (
>   IN CHAR16  *Str2
>   )
> {
> +  ASSERT (gUnicodeCollationInterface != NULL);
>   return gUnicodeCollationInterface->StriColl (gUnicodeCollationInterface, Str1, Str2);
> }

Off-topic (should merge either way), but is there a reason such a function is not in BaseLib?
@Ard Do you happen to know?

> /**
> @@ -761,6 +753,19 @@ Ext4Bind (
>   BlockIo = NULL;
>   DiskIo  = NULL;
> 
> +  // Note: We initialize collation here since this is called in BDS, when we are likely
> +  // to have the Unicode Collation protocols available.
> +  if (!Ext4IsCollationInitialized ()) {

Why do we need to expose this? I.e., why can't this be an internal decision of Ext4InitialiseUnicodeCollation()?

> +    Status = Ext4InitialiseUnicodeCollation (BindingProtocol->ImageHandle);


  reply	other threads:[~2023-02-18 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 20:14 [PATCH 1/1] Ext4Pkg: Move unicode collation initialization to Start() Pedro Falcato
2023-02-18 12:30 ` Marvin Häuser [this message]
2023-02-18 15:14   ` Pedro Falcato
2023-02-18 17:04     ` Marvin Häuser
2023-02-20  7:52 ` Ard Biesheuvel
2023-02-20  8:00   ` Marvin Häuser
2023-02-21 19:25     ` Pedro Falcato
2023-02-21 19:37       ` Marvin Häuser
2023-02-24  0:34         ` Pedro Falcato

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-list 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=EF2BDE6E-B565-423C-B05C-8B9DE2231DF5@posteo.de \
    --to=devel@edk2.groups.io \
    /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