public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Leif Lindholm <leif@nuviainc.com>
Cc: devel@edk2.groups.io, Samer.El-Haj-Mahmoud@arm.com
Subject: Re: [PATCH edk2-platforms 0/2] SynQuacer: fix driver model integration of NetSec
Date: Thu, 9 Apr 2020 07:48:57 +0200	[thread overview]
Message-ID: <52332a8a-1e46-cee0-ca17-4c213d66bf0d@arm.com> (raw)
In-Reply-To: <20200408162607.GW14075@vanye>

On 4/8/20 6:26 PM, Leif Lindholm wrote:
> On Wed, Apr 08, 2020 at 18:11:36 +0200, Ard Biesheuvel wrote:
>> Currently, the way the SynQuacer NetSec driver implements the EFI driver
>> model is slightly quirky. Two changes are needed to move it closer to the
>> intent of the driver model, which is the ability to boot using only the
>> drivers that are required to drive the devices that are needed at boot.
>> This series does not complete the picture entirely yet for SynQuacer, and
>> it still relies on the unconditional EfiBootManagerConnectAll() call that
>> exists in the PlatformBootManagerLib implementation in ArmPkg. This is left
>> for future work.
>>
>> Ard Biesheuvel (2):
>>    Silicon/SynQuacer/PlatformDxe: defer device registration until
>>      EndOfDxe
>>    Silicon/SynQuacer/NetsecDxe: move device path to root device
> 
> LGTM.
> 
> For the series:
> Reviewed-by: Leif Lindholm <leif@nuviainc.com>
> 
> 

Thanks. Series pushed.

      reply	other threads:[~2020-04-09  5:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 16:11 [PATCH edk2-platforms 0/2] SynQuacer: fix driver model integration of NetSec Ard Biesheuvel
2020-04-08 16:11 ` [PATCH edk2-platforms 1/2] Silicon/SynQuacer/PlatformDxe: defer device registration until EndOfDxe Ard Biesheuvel
2020-04-08 16:11 ` [PATCH edk2-platforms 2/2] Silicon/SynQuacer/NetsecDxe: move device path to root device Ard Biesheuvel
2020-04-08 16:26 ` [PATCH edk2-platforms 0/2] SynQuacer: fix driver model integration of NetSec Leif Lindholm
2020-04-09  5:48   ` Ard Biesheuvel [this message]

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=52332a8a-1e46-cee0-ca17-4c213d66bf0d@arm.com \
    --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