From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4F779C2D0D1 for ; Thu, 19 Dec 2019 23:24:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2586824679 for ; Thu, 19 Dec 2019 23:24:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576797878; bh=K3CvbaB8eN/Eb3ZiDlzpb2f2O7TIhZPxnGG8BvCApZA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=03nhktAFpH05eDH/cTCWXOpVnlWogG2WUlHKFOLkcGL2AroIq519gF/5jQWYTJFKq NxLmnGOvMKsu+IUL3u6+n6PHLXM+HFQ94aqXRvysv35onbL3zuNFrTkW+/AwjJES8w 6IbzlCsP4653jhR+cod/Ztn6BwdpzPhknHwgfH0I= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727129AbfLSXYh (ORCPT ); Thu, 19 Dec 2019 18:24:37 -0500 Received: from mail.kernel.org ([198.145.29.99]:59268 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726880AbfLSXYh (ORCPT ); Thu, 19 Dec 2019 18:24:37 -0500 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 20EC624676; Thu, 19 Dec 2019 23:24:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576797876; bh=K3CvbaB8eN/Eb3ZiDlzpb2f2O7TIhZPxnGG8BvCApZA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XAspA5fA3wS6cyzuttDwywfqalB85K4DEU1gYdSGJKg97fof11phNpx85w8Z6Rwc+ mhpmUK7TrloulsZiMb/hnrx297BtyaM0DEwZVHp97YKu27zY2uQVJiHo/LLPws1Vay ll3fTOlmTdBw9u4lL/Lwt9f+viCPxQWQgBa9LnXU= Date: Thu, 19 Dec 2019 18:24:35 -0500 From: Sasha Levin To: Ard Biesheuvel Cc: Linux Kernel Mailing List , stable , Ard Biesheuvel , Masahiro Yamada , Herbert Xu , linux-arm-kernel , linux-riscv@lists.infradead.org, "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" Subject: Re: [PATCH AUTOSEL 5.4 316/350] int128: move __uint128_t compiler test to Kconfig Message-ID: <20191219232435.GU17708@sasha-vm> References: <20191210210735.9077-1-sashal@kernel.org> <20191210210735.9077-277-sashal@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 11, 2019 at 10:07:54AM +0000, Ard Biesheuvel wrote: >On Tue, 10 Dec 2019 at 22:13, Sasha Levin wrote: >> >> From: Ard Biesheuvel >> >> [ Upstream commit c12d3362a74bf0cd9e1d488918d40607b62a3104 ] >> >> In order to use 128-bit integer arithmetic in C code, the architecture >> needs to have declared support for it by setting ARCH_SUPPORTS_INT128, >> and it requires a version of the toolchain that supports this at build >> time. This is why all existing tests for ARCH_SUPPORTS_INT128 also test >> whether __SIZEOF_INT128__ is defined, since this is only the case for >> compilers that can support 128-bit integers. >> >> Let's fold this additional test into the Kconfig declaration of >> ARCH_SUPPORTS_INT128 so that we can also use the symbol in Makefiles, >> e.g., to decide whether a certain object needs to be included in the >> first place. >> >> Cc: Masahiro Yamada >> Signed-off-by: Ard Biesheuvel >> Signed-off-by: Herbert Xu >> Signed-off-by: Sasha Levin > >This does not fix a bug so no need to put it in -stable Dropped, thanks! -- Thanks, Sasha