From: Ingo Molnar <mingo@kernel.org>
To: Matt Fleming <matt@console-pimps.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] EFI changes
Date: Mon, 28 Oct 2013 12:17:41 +0100 [thread overview]
Message-ID: <20131028111741.GA7830@gmail.com> (raw)
In-Reply-To: <20131027214815.GH1982@console-pimps.org>
* Matt Fleming <matt@console-pimps.org> wrote:
> Guys, do you think we could get the EFI earlyprintk support into the
> 'x86/efi' branch for the upcoming merge window? I know it's quite late
> in the game but since it's a new feature it shouldn't introduce any kind
> of regression and is a much needed feature.
>
> The following changes since commit c158c3bf59951bbb44bd7ccca9e6665dfd1617c5:
>
> boot, efi: Remove redundant memset() (2013-10-04 20:07:47 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next
>
> for you to fetch changes up to 32c9e70fc3912c3b9c7d53ce016960ce99ff93d4:
>
> x86/efi: Add EFI framebuffer earlyprintk support (2013-10-27 21:18:48 +0000)
This breaks on x86-64 allmodconfig with:
arch/x86/built-in.o: In function `early_efi_setup':
early_printk.c:(.init.text+0x27e9f): undefined reference to `get_default_font'
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-28 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 21:48 [GIT PULL] EFI changes Matt Fleming
2013-10-28 11:17 ` Ingo Molnar [this message]
2013-10-28 11:49 ` Matt Fleming
2013-10-28 11:50 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2013-10-29 8:18 Matt Fleming
2013-10-28 12:35 Matt Fleming
2013-10-28 13:44 ` Ingo Molnar
2013-10-28 15:52 ` Matt Fleming
2013-10-28 15:55 ` Ingo Molnar
2013-10-28 20:30 ` Matt Fleming
2013-10-29 8:11 ` Ingo Molnar
2013-10-04 19:55 Matt Fleming
2013-10-06 9:27 ` Ingo Molnar
2013-09-30 10:49 Matt Fleming
2013-09-30 14:26 ` H. Peter Anvin
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=20131028111741.GA7830@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).