Re: [edk2] [PATCH] ArmVirtPkg: undo bogus component name and driver diagnostics disablement

2016-10-15 Thread Laszlo Ersek
On 10/15/16 18:58, Ard Biesheuvel wrote: > On 15 October 2016 at 17:56, Laszlo Ersek wrote: >> The entry point function of any UEFI_DRIVER that conforms to the UEFI >> driver model must install an instance of the EFI_DRIVER_BINDING_PROTOCOL >> on the image handle. Beyond that,

Re: [edk2] [PATCH] ArmVirtPkg: undo bogus component name and driver diagnostics disablement

2016-10-15 Thread Ard Biesheuvel
On 15 October 2016 at 17:56, Laszlo Ersek wrote: > The entry point function of any UEFI_DRIVER that conforms to the UEFI > driver model must install an instance of the EFI_DRIVER_BINDING_PROTOCOL > on the image handle. Beyond that, the following protocols are optional: > > -

[edk2] [PATCH] ArmVirtPkg: undo bogus component name and driver diagnostics disablement

2016-10-15 Thread Laszlo Ersek
The entry point function of any UEFI_DRIVER that conforms to the UEFI driver model must install an instance of the EFI_DRIVER_BINDING_PROTOCOL on the image handle. Beyond that, the following protocols are optional: - EFI_COMPONENT_NAME_PROTOCOL - EFI_COMPONENT_NAME2_PROTOCOL -