From: jcm@redhat.com (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: fixes for -rc6
Date: Tue, 11 Apr 2017 15:12:57 -0400 [thread overview]
Message-ID: <3b32cfd3-7675-005b-a737-58a8677f65ac@redhat.com> (raw)
In-Reply-To: <20170407160239.GS19342@arm.com>
On 04/07/2017 12:02 PM, Will Deacon wrote:
> Please pull these two arm64 fixes for -rc6. We've got a regression fix for
> the signal raised when userspace makes an unsupported unaligned access and a
> revert of the contiguous (hugepte) support for hugetlb, which has once again
> been found to be broken. One day, maybe, we'll get it right.
<snip>
> - Revert broken support for the contiguous bit in hugetlb (again...)
Quick aside: is this being worked on for 4.12? If not, should we ping
Linaro and look to get some focus on this? It's right to disable this,
but also painful to those wanting to work on various NFV use cases.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2017-04-11 19:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 16:02 [GIT PULL] arm64: fixes for -rc6 Will Deacon
2017-04-11 19:12 ` Jon Masters [this message]
2017-04-12 9:14 ` Will Deacon
2017-04-12 10:18 ` Punit Agrawal
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 10:25 [GIT PULL] arm64 " Will Deacon
2024-02-23 18:44 ` pr-tracker-bot
2023-06-08 20:51 Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2021-12-15 11:19 Will Deacon
2021-12-15 16:00 ` Catalin Marinas
2021-12-15 18:49 ` Linus Torvalds
2020-11-27 11:40 Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon
2019-06-20 19:10 ` pr-tracker-bot
2019-02-08 17:35 Will Deacon
2019-02-09 0:40 ` pr-tracker-bot
2015-10-15 13:38 Will Deacon
2015-01-23 16:44 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=3b32cfd3-7675-005b-a737-58a8677f65ac@redhat.com \
--to=jcm@redhat.com \
--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).