linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>
Cc: Alan Ott <alan@softiron.co.uk>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	Roy Franz <roy.franz@linaro.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Matt Fleming <matt@codeblueprint.co.uk>
Subject: [PATCH 2/4] doc: efi-stub.txt: Fix arm64 paths
Date: Mon, 14 Dec 2015 18:26:51 +0000	[thread overview]
Message-ID: <1450117613-15438-3-git-send-email-matt@codeblueprint.co.uk> (raw)
In-Reply-To: <1450117613-15438-1-git-send-email-matt@codeblueprint.co.uk>

From: Alan Ott <alan@softiron.co.uk>

Update documented paths for arm64 files to match current tree.

Signed-off-by: Alan Ott <alan@softiron.co.uk>
Cc: Roy Franz <roy.franz@linaro.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
---
 Documentation/efi-stub.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/efi-stub.txt b/Documentation/efi-stub.txt
index 7747024d3bb7..e15746988261 100644
--- a/Documentation/efi-stub.txt
+++ b/Documentation/efi-stub.txt
@@ -10,12 +10,12 @@ arch/x86/boot/header.S and arch/x86/boot/compressed/eboot.c,
 respectively. For ARM the EFI stub is implemented in
 arch/arm/boot/compressed/efi-header.S and
 arch/arm/boot/compressed/efi-stub.c. EFI stub code that is shared
-between architectures is in drivers/firmware/efi/efi-stub-helper.c.
+between architectures is in drivers/firmware/efi/libstub.
 
 For arm64, there is no compressed kernel support, so the Image itself
 masquerades as a PE/COFF image and the EFI stub is linked into the
 kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
-and arch/arm64/kernel/efi-stub.c.
+and drivers/firmware/efi/libstub/arm64-stub.c.
 
 By using the EFI boot stub it's possible to boot a Linux kernel
 without the use of a conventional EFI boot loader, such as grub or
-- 
2.6.2

  parent reply	other threads:[~2015-12-14 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 18:26 [GIT PULL 0/4] EFI changes for v4.5 Matt Fleming
2015-12-14 18:26 ` [PATCH 1/4] efi/esrt: Don't preformat name Matt Fleming
2015-12-14 18:26 ` Matt Fleming [this message]
     [not found]   ` <1450117613-15438-3-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-15  7:32     ` [PATCH 2/4] doc: efi-stub.txt: Fix arm64 paths Ard Biesheuvel
     [not found] ` <1450117613-15438-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-14 18:26   ` [PATCH 3/4] x86/efi: Preface all print statements with efi* tag Matt Fleming
2015-12-14 18:26 ` [PATCH 4/4] x86/efi-bgrt: Fix kernel panic when mapping BGRT data 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=1450117613-15438-3-git-send-email-matt@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=alan@softiron.co.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=corbet@lwn.net \
    --cc=hpa@zytor.com \
    --cc=leif.lindholm@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=roy.franz@linaro.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).