From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request for UEFI sub-system for v2019.07-rc2 (2)
Date: Wed, 8 May 2019 13:50:53 -0400 [thread overview]
Message-ID: <20190508175053.GR25571@bill-the-cat> (raw)
In-Reply-To: <302b84e3-4ac7-25ad-3eba-b624ad48eb23@gmx.de>
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190508/55327928/attachment.sig>
next parent reply other threads:[~2019-05-08 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <302b84e3-4ac7-25ad-3eba-b624ad48eb23@gmx.de>
2019-05-08 17:50 ` Tom Rini [this message]
2019-05-08 22:03 ` [U-Boot] Pull request for UEFI sub-system for v2019.07-rc2 (2) Heinrich Schuchardt
2019-05-08 22:06 ` Tom Rini
2019-05-08 22:15 ` Graf, Alexander
2019-05-09 11:27 ` Tom Rini
2019-05-09 14:16 ` Tom Rini
2019-05-09 16:05 ` Heinrich Schuchardt
2019-05-09 16:10 ` Tom Rini
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-all 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=20190508175053.GR25571@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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