From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: module: add support for R_ARM_REL32 relocations
Date: Thu, 19 Jan 2017 23:56:42 +0000 [thread overview]
Message-ID: <20170119235642.GK27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1484863892-5818-1-git-send-email-ard.biesheuvel@linaro.org>
On Thu, Jan 19, 2017 at 10:11:32PM +0000, Ard Biesheuvel wrote:
> Add support for R_ARM_REL32 relocations in the module loader,
> which will be used by the modversions code when (if) it switches
> to using relative references to refer to CRC values.
Thanks, please keep this patch handy for when (if) that does happen.
I won't apply this until it is actually needed - no point adding stuff
that never gets used (and therefore doesn't get tested.)
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-01-19 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 22:11 [PATCH] arm: module: add support for R_ARM_REL32 relocations Ard Biesheuvel
2017-01-19 23:56 ` Russell King - ARM Linux [this message]
2017-01-20 10:28 ` Ard Biesheuvel
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=20170119235642.GK27312@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).