From: mpe@ellerman.id.au (Michael Ellerman)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 1/3] futex: remove duplicated code
Date: Sat, 04 Mar 2017 23:49:44 +1100 [thread overview]
Message-ID: <877f45cil2.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170303122712.13353-1-jslaby@suse.cz>
Jiri Slaby <jslaby at suse.cz> writes:
> There is code duplicated over all architecture's headers for
> futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr,
> and comparison of the result.
>
> Remove this duplication and leave up to the arches only the needed
> assembly which is now in arch_futex_atomic_op_inuser.
Looks OK and boots on powerpc. But I don't think anything's actually
calling those futex ops. Is there a test suite I should run?
Acked-by: Michael Ellerman <mpe at ellerman.id.au> (powerpc)
cheers
next prev parent reply other threads:[~2017-03-04 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 12:27 [PATCH 1/3] futex: remove duplicated code Jiri Slaby
2017-03-03 14:08 ` Heiko Carstens
2017-03-03 14:48 ` Chris Metcalf
2017-03-04 12:49 ` Michael Ellerman [this message]
2017-03-04 13:05 ` Russell King - ARM Linux
2017-03-04 19:15 ` H. Peter Anvin
2017-03-04 21:38 ` Stafford Horne
2017-03-04 23:03 ` H. Peter Anvin
2017-03-04 23:08 ` H. Peter Anvin
2017-03-09 4:16 ` Rob Landley
2017-03-09 4:36 ` H. Peter Anvin
2017-03-06 1:52 ` Rich Felker
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=877f45cil2.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-snps-arc@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