From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>,
Andrey Konovalov <andreyknvl@google.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Dave P Martin <Dave.Martin@arm.com>,
Dave Hansen <dave.hansen@intel.com>,
linux-doc@vger.kernel.org, linux-arch@vger.kernel.org
Subject: [PATCH v10 0/1] arm64 tagged address ABI
Date: Fri, 23 Aug 2019 17:37:16 +0100 [thread overview]
Message-ID: <20190823163717.19569-1-catalin.marinas@arm.com> (raw)
Hi,
Minor update to the arm64 tagged address ABI documentation since v9,
posted here:
http://lkml.kernel.org/r/20190821164730.47450-1-catalin.marinas@arm.com
The mmap/mremap/... patch (1/3) has been queued in the -mm tree and
removed from this series. The tagged-address-abi.rst patch (2/3) has
been queued in the arm64 for-next/core tree. There is only one patch
left in this series (keeping the cover letter for consistency).
Changes in v10:
- Remove the tag preservation paragraph since the new ABI does not
change the behaviour we already have. The only difference is that now
the kernel can access tagged addresses (e.g. delivering a signal on a
tagged alternate stack).
Vincenzo Frascino (1):
arm64: Relax Documentation/arm64/tagged-pointers.rst
Documentation/arm64/tagged-pointers.rst | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)
next reply other threads:[~2019-08-23 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 16:37 Catalin Marinas [this message]
2019-08-23 16:37 ` [PATCH v10 1/1] arm64: Relax Documentation/arm64/tagged-pointers.rst Catalin Marinas
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=20190823163717.19569-1-catalin.marinas@arm.com \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dave.hansen@intel.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=szabolcs.nagy@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.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