On Wed, May 08, 2019 at 07:57:57AM +0200, Heinrich Schuchardt wrote:

> The following changes since commit 44237e272f1eac3b026709e76333a07b2d3a3523:
> 
>   Merge branch 'master' of git://git.denx.de/u-boot-sh (2019-05-06
> 07:19:31 -0400)
> 
> are available in the Git repository at:
> 
>   git://git.denx.de/u-boot-efi.git tags/efi-2019-07-rc2-2
> 
> for you to fetch changes up to b015ab57bf558daa1c768995a7a7f1df2d40191e:
> 
>   efi_loader: signature of ExitBootServices() (2019-05-07 21:10:04 +0200)
> 
> Travis CI results are here:
> https://travis-ci.org/xypron2/u-boot/builds/529448555
> 
> Primary key fingerprint:
> 6DC4 F9C7 1F29 A6FA 06B7  6D33 C481 DBBC 2C05 1AC4
> 

Note that you may want to run ./scripts/checkpatch.pl --git
origin/master.. or similar as:
WARNING: 'follwing' may be misspelled - perhaps 'following'?

which I left alone rather than mess up the tag.

Applied to u-boot/master, thanks!

And all of that said, looking over my before/after builds I see a lot of
size growth, everywhere, due to EFI changes.  I assume this is due to
increasing overall functionality and support, which is good.  But is
there perhaps some way we can split things into a minimal "we have
enough to support loading ${OS LOADER}" and then "we are aiming for
large parts of spec compliance" ?  Some days I start to wonder if
"EFI_LOADER on by default" was a bad idea.

-- 
Tom

Attachment: signature.asc
Description: PGP signature

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to