From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add support ARCH_SUPPORTS_INT128
Date: Tue, 21 Jun 2016 16:14:05 +0100 [thread overview]
Message-ID: <20160621151404.GD14542@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1466492123-3356-1-git-send-email-wangkefeng.wang@huawei.com>
On Tue, Jun 21, 2016 at 02:55:23PM +0800, Kefeng Wang wrote:
> The gcc support __SIZEOF_INT128__ and __int128 in arm64, thus,
> enable ARCH_SUPPORTS_INT128 to make mul_u64_u32_shr() a bit
> more efficient in scheduler.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Queued for 4.8. Thanks.
--
Catalin
next prev parent reply other threads:[~2016-06-21 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 6:55 [PATCH] arm64: Add support ARCH_SUPPORTS_INT128 Kefeng Wang
2016-06-21 15:14 ` Catalin Marinas [this message]
2016-06-22 10:57 ` Catalin Marinas
2016-06-22 12:43 ` Will Deacon
2016-06-22 13:43 ` Catalin Marinas
2016-06-22 13:23 ` Ard Biesheuvel
2016-06-23 3:23 ` Kefeng Wang
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=20160621151404.GD14542@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@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 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).