From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: get rid of TEXT_OFFSET
Date: Mon, 7 Sep 2020 14:59:53 +0100 [thread overview]
Message-ID: <20200907135953.GA12785@willie-the-truck> (raw)
In-Reply-To: <30a43ae2-4b3b-c8b9-aea4-fd404c64dbd9@arm.com>
On Wed, Sep 02, 2020 at 12:19:44PM +0530, Anshuman Khandual wrote:
> On 08/25/2020 07:24 PM, Ard Biesheuvel wrote:
> > TEXT_OFFSET serves no purpose, and for this reason, it was redefined
> > as 0x0 in the v5.8 timeframe. Since this does not appear to have caused
> > any issues that require us to revisit that decision, let's get rid of the
> > macro entirely, along with any references to it.
> >
> > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > ---
> > arch/arm64/Makefile | 6 ------
> > arch/arm64/include/asm/boot.h | 3 +--
> > arch/arm64/include/asm/kernel-pgtable.h | 2 +-
> > arch/arm64/include/asm/memory.h | 2 +-
> > arch/arm64/kernel/Makefile | 2 --
> > arch/arm64/kernel/head.S | 16 ++++++----------
> > arch/arm64/kernel/image.h | 1 -
> > arch/arm64/kernel/vmlinux.lds.S | 4 ++--
> > drivers/firmware/efi/libstub/Makefile | 1 -
> > drivers/firmware/efi/libstub/arm64-stub.c | 6 +++---
> > 10 files changed, 14 insertions(+), 29 deletions(-)
>
> Documentation/arm64/booting.rst needs an update ?
What specifically do you think needs updating?
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-07 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 13:54 [PATCH] arm64: get rid of TEXT_OFFSET Ard Biesheuvel
2020-09-02 6:49 ` Anshuman Khandual
2020-09-07 13:59 ` Will Deacon [this message]
2020-09-07 16:05 ` Will Deacon
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=20200907135953.GA12785@willie-the-truck \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.