From: Arnd Bergmann <arnd@arndb.de>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
tglx@linutronix.de, x86@kernel.org, linux-arch@vger.kernel.org,
mgorman@techsingularity.net, linux-api@vger.kernel.org,
linux-mm@kvack.org, luto@kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] generic syscalls: kill cruft from removed pkey syscalls
Date: Mon, 17 Oct 2016 17:37:29 +0200 [thread overview]
Message-ID: <5993847.hpzj164ak1@wuerfel> (raw)
In-Reply-To: <20161017151814.1CE8B6C3@viggo.jf.intel.com>
On Monday, October 17, 2016 8:18:15 AM CEST Dave Hansen wrote:
>
> pkey_set() and pkey_get() were syscalls present in older versions
> of the protection keys patches. They were fully excised from the
> x86 code, but some cruft was left in the generic syscall code. The
> C++ comments were intended to help to make it more glaring to me to
> fix them before actually submitting them. That technique worked,
> but later than I would have liked.
>
> I test-compiled this for arm64.
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: x86@kernel.org
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: linux-arch@vger.kernel.org
> Cc: mgorman@techsingularity.net
> Cc: linux-api@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: luto@kernel.org
> Cc: akpm@linux-foundation.org
> Cc: torvalds@linux-foundation.org
> Fixes: a60f7b69d92c0 ("generic syscalls: Wire up memory protection keys syscalls")
Acked-by: Arnd Bergmann <arnd@arndb.de>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-10-17 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 15:18 Dave Hansen
2016-10-17 15:37 ` Arnd Bergmann [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=5993847.hpzj164ak1@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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