From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: fix for -rc3
Date: Fri, 7 Sep 2018 16:45:16 +0100 [thread overview]
Message-ID: <20180907154516.GG12788@arm.com> (raw)
Hi Linus,
Just one small fix here, preventing a VM_WARN_ON when a !present PMD/PUD
is "freed" as part of a huge ioremap() operation. The correct behaviour
is to skip the free silently in this case, which is a little weird (the
function is a bit of a misnomer), but it follows the x86 implementation.
I also renewed the expiry dates on my gpg subkeys this week, so you might
need to re-fetch them if you can find a working keyserver.
Cheers,
Will
--->8
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to fac880c7d074fdfca874114b5c47b36aa034e4ee:
arm64: fix erroneous warnings in page freeing functions (2018-09-06 18:01:13 +0100)
----------------------------------------------------------------
arm64 fix
- Remove accidental VM_WARN_ON
----------------------------------------------------------------
Mark Rutland (1):
arm64: fix erroneous warnings in page freeing functions
arch/arm64/mm/mmu.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: [GIT PULL] arm64: fix for -rc3
Date: Fri, 7 Sep 2018 16:45:16 +0100 [thread overview]
Message-ID: <20180907154516.GG12788@arm.com> (raw)
Hi Linus,
Just one small fix here, preventing a VM_WARN_ON when a !present PMD/PUD
is "freed" as part of a huge ioremap() operation. The correct behaviour
is to skip the free silently in this case, which is a little weird (the
function is a bit of a misnomer), but it follows the x86 implementation.
I also renewed the expiry dates on my gpg subkeys this week, so you might
need to re-fetch them if you can find a working keyserver.
Cheers,
Will
--->8
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to fac880c7d074fdfca874114b5c47b36aa034e4ee:
arm64: fix erroneous warnings in page freeing functions (2018-09-06 18:01:13 +0100)
----------------------------------------------------------------
arm64 fix
- Remove accidental VM_WARN_ON
----------------------------------------------------------------
Mark Rutland (1):
arm64: fix erroneous warnings in page freeing functions
arch/arm64/mm/mmu.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
next reply other threads:[~2018-09-07 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 15:45 Will Deacon [this message]
2018-09-07 15:45 ` [GIT PULL] arm64: fix for -rc3 Will Deacon
2018-09-07 17:51 ` Linus Torvalds
2018-09-07 17:51 ` Linus Torvalds
2018-09-10 17:45 ` Will Deacon
2018-09-10 17:45 ` Will Deacon
2018-09-11 18:45 ` Linus Torvalds
2018-09-11 18:45 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2016-06-10 13:38 Will Deacon
2016-06-10 13:38 ` 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=20180907154516.GG12788@arm.com \
--to=will.deacon@arm.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 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.