From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: module: handle negative R_ARM_PREL31 addends correctly
Date: Mon, 30 Jan 2017 16:26:28 +0000 [thread overview]
Message-ID: <20170130162628.GD27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAKv+Gu-0J0tVUUDhJ_f1P9n-1Etgk5A6ZTgUokKu7RKOCeaW4g@mail.gmail.com>
On Mon, Jan 30, 2017 at 03:08:56PM +0000, Ard Biesheuvel wrote:
> Actually, I think it may still be incorrect: it seems to me that we
> should preserve bit 31 rather than clear it. From the EHABI
Agreed.
--
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.
prev parent reply other threads:[~2017-01-30 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 10:21 [PATCH] arm: module: handle negative R_ARM_PREL31 addends correctly Ard Biesheuvel
2017-01-30 12:39 ` Russell King - ARM Linux
2017-01-30 15:08 ` Ard Biesheuvel
2017-01-30 16:26 ` Russell King - ARM Linux [this message]
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=20170130162628.GD27312@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).