From: Dave Young <dyoung@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
x86@kernel.org, mjg59@srcf.ucam.org, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, vgoyal@redhat.com,
ebiederm@xmission.com, horms@verge.net.au,
kexec@lists.fedoraproject.org, kexec@lists.infradead.org
Subject: Re: [patch 3/6] Cleanup efi_enter_virtual_mode function
Date: Mon, 28 Oct 2013 19:24:58 +0800 [thread overview]
Message-ID: <20131028112458.GD29133@dhcp-16-126.nay.redhat.com> (raw)
In-Reply-To: <20131028112045.GH4314@pd.tnic>
On 10/28/13 at 12:20pm, Borislav Petkov wrote:
> On Mon, Oct 28, 2013 at 06:10:11PM +0800, Dave Young wrote:
> > Sorry, I have not any public git account. Attached the patch I applied
> > with git
>
> Still doesn't work:
>
> $ patch -p1 --dry-run -i /tmp/02-efi-enter-virtual-mode-cleanup-1.patch.new
> checking file arch/x86/platform/efi/efi.c
> Hunk #1 succeeded at 788 (offset -1 lines).
> Hunk #2 succeeded at 821 (offset -1 lines).
> Hunk #3 FAILED at 853.
> 1 out of 3 hunks FAILED
>
> I'm using Matt's next branch + my efi runtime branch. What are you
> basing your stuff ontop?
I use linus tree, git pull Matt's efi-next tree, then apply your 12 patches
and my patches. I applied your previous 11 patches + the last update patch
12/12, but the last one does not apply, I manually shift a hunk to make it
apply.
next prev parent reply other threads:[~2013-10-28 11:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 3:47 [patch 0/6] kexec kernel efi runtime support dyoung
2013-10-27 3:47 ` [patch 1/6] Add function efi_remap_region for remapping to saved virt address dyoung
2013-10-27 11:50 ` Borislav Petkov
2013-10-28 1:25 ` Dave Young
2013-10-27 3:47 ` [patch 3/6] Cleanup efi_enter_virtual_mode function dyoung
2013-10-28 9:32 ` Borislav Petkov
2013-10-28 9:40 ` Dave Young
2013-10-28 9:51 ` Dave Young
2013-10-28 10:04 ` Borislav Petkov
2013-10-28 10:10 ` Dave Young
2013-10-28 10:39 ` Dave Young
2013-10-28 11:20 ` Borislav Petkov
2013-10-28 11:24 ` Dave Young [this message]
2013-10-28 14:58 ` Borislav Petkov
2013-10-28 15:10 ` Dave Young
2013-10-29 2:32 ` Dave Young
2013-10-29 13:43 ` Borislav Petkov
2013-10-30 2:03 ` Dave Young
2013-10-30 10:47 ` Borislav Petkov
2013-10-31 2:04 ` Dave Young
2013-10-31 2:07 ` Dave Young
2013-10-31 3:07 ` H. Peter Anvin
2013-10-31 10:45 ` Borislav Petkov
2013-11-01 1:15 ` Dave Young
2013-10-31 10:44 ` Borislav Petkov
2013-11-01 1:18 ` Dave Young
2013-11-01 11:32 ` Borislav Petkov
2013-10-27 3:47 ` [patch 4/6] export more efi table variable to sysfs dyoung
2013-10-27 3:47 ` [patch 5/6] export efi runtime memory mapping " dyoung
2013-10-29 5:34 ` Dave Young
2013-10-27 3:47 ` [patch 6/6] passing kexec necessary efi data via setup_data dyoung
[not found] ` <20131027035922.924386710@dhcp-16-126.nay.redhat.com>
2013-10-27 10:50 ` [patch 2/6] x86 efi: reserve boot service fix Borislav Petkov
2013-10-27 20:30 ` Matt Fleming
2013-10-28 1:18 ` Dave Young
2013-10-28 8:44 ` Borislav Petkov
2013-10-28 10:27 ` Matt Fleming
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=20131028112458.GD29133@dhcp-16-126.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bp@alien8.de \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.fedoraproject.org \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
/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).