Series Reviewed-by: Jordan Justen
On 2016-10-12 03:09:00, Laszlo Ersek wrote:
> Reviewing (part of) Ray's recent FrameBufferBltLib changes gave me the
> idea for this. The patches are really small.
>
> Public branch:
On 2016-10-13 02:29:46, Yonghong Zhu wrote:
> This patch updates PatchCheck.py:
Can you split this into 3 separate patches?
> 1.Update max line length to 70 that describe in wiki
I think we should update PatchCheck.py and the wiki to say that:
1. The subject line of the commit message should
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,
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:
>
> -
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
-
Hi guys
I've created an uefi application in a directory that is not inside the
EDK2015 folder.
For example:
My UDK folder is:
C:\Projects\UEFI\UDK2015_r18552
|- BaseTools
|- Conf
|- CryptoPkg
|-etc
My Uefi app is on:
C:\Projects\UEFI\Projects\MyApp
|- EntryPoint.c
|- MyApp.dsc
|- .etc
Of course, it is fine to give a good name in MdePkg. :)
My concern is only about "Compatibility".
This series patch only updated ArmPkg and EmbeddedPkg.
But there might be more close source IP protected packages using the original
header file.
That is why I propose a compatible way: We give a
7 matches
Mail list logo