Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp1118812imn; Sat, 30 Jul 2022 16:21:38 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uWB/jPHcHiSVKXQrOWyoGuN5kkEo/CVdvbCrKIjKVlJfMpHaYXXkyECkvSweoWyVpX6p9l X-Received: by 2002:a17:907:a06f:b0:72b:564c:465b with SMTP id ia15-20020a170907a06f00b0072b564c465bmr7638402ejc.344.1659223298575; Sat, 30 Jul 2022 16:21:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659223298; cv=none; d=google.com; s=arc-20160816; b=RofQJcNkrtfe5sj50lZD3pdLL2vmYzUcNdGKPjtBGwMoSWhQUC0DY8taWzeAUfn3YA XwiKRXOpgIOc5fy3LmKyhjGgVkXMShWZ2rWFi7MjWRtrDIgTld2HMO/8eKU1srcJLZxi Ny1XetYeyOlQ4qMs85ME6DyIz7VGrMGxstov0gyt0aOrm5H2bkvkXe/sGvfvDXpztf+4 PX5f1bUodoRTpeaocO+XoA50QRhT+YPRWBH23dc8SUdMIxK+0pLHtnAFFIGl45BLnLH2 uOB+vYk9mmaRbBDFGC+sRtUrRWbQGpBWwHFUqnKL9ALBf0ehyLV6VpI8kp/hDwWdwIV9 oCOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=AzCdRPj05yjL8h85+6gig1pAniprat2lIv4CqlJ0538=; b=fb5PaMTQoIZT8JlUhGEiyd4e4+CRCDx9JOGh9ACO3kW4baRHHCC5939WgesygY0b7m uKzo0b7Sk2dmaID7FRaBcFZwzZ1xVividiqG+QGqNDIWsGH+oxH4UkZM6DdNVf4SaOBo 4ejBg0zAigsLRckbPPk2yr7bKCF4gvBSKHQEtnLT1QN6H9skObqg/4cN62i2rb2C83dk LEYQzo+qkfQh9/1gUjgrORCkBCzjjhpzUY5bxyKoQuv8Le/HJhbeupj1Z92F6JekSqTM oe1g3G5nRPtXVPHyhFibWI7GeEsS0kSBxiTMJ2szbUl/f7aF5AKmx/ItUdutA/QAKIh5 Sh1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=SUdHm9Vd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=zx2c4.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u19-20020a1709064ad300b0072b88d59ce5si5574781ejt.461.2022.07.30.16.20.53; Sat, 30 Jul 2022 16:21:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=SUdHm9Vd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232779AbiG3XQK (ORCPT + 99 others); Sat, 30 Jul 2022 19:16:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39506 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230432AbiG3XQI (ORCPT ); Sat, 30 Jul 2022 19:16:08 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4AA6365F5 for ; Sat, 30 Jul 2022 16:16:07 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D7E3260FCB for ; Sat, 30 Jul 2022 23:16:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C887C433C1; Sat, 30 Jul 2022 23:16:05 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="SUdHm9Vd" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1659222963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=AzCdRPj05yjL8h85+6gig1pAniprat2lIv4CqlJ0538=; b=SUdHm9VdcBySkgCGqKK/SvTxdxaNdVZYwa4T1eNvhkLbUlm7F3tOQ3EUNsh2phAGbQZx2K VBQPiV/0m3zyeXpM22Lvzg5igCOEd8/snd4QY65ABaVLJjBe5TyR+HHiFg1q+GpSAmuq2k zigzuYJno3uB5FW3QMZon4YKaeGjwMs= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id f4e515bd (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 30 Jul 2022 23:16:03 +0000 (UTC) Date: Sun, 31 Jul 2022 01:15:59 +0200 From: "Jason A. Donenfeld" To: Greg Kroah-Hartman Cc: Arnd Bergmann , Ard Biesheuvel , kernel test robot , "Justin M. Forbes" , clang-built-linux , kbuild-all@lists.01.org, Linux Kernel Mailing List , "Jason A. Donenfeld" Subject: Re: [linux-stable-rc:linux-5.15.y 6874/8723] arch/arm/lib/xor-neon.c:30:2: warning: This code requires at least version 4.6 of GCC Message-ID: References: <202207250449.BYMZbIA2-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 30, 2022 at 04:33:28PM +0200, Greg Kroah-Hartman wrote: > On Mon, Jul 25, 2022 at 04:35:38PM +0200, Arnd Bergmann wrote: > > On Mon, Jul 25, 2022 at 2:55 PM Arnd Bergmann wrote: > > > > > The other easy workaround would be to just turn off the xor-neon code > > > when building with clang, e.g. using this Makefile hack: > > > > > > diff --git a/arch/arm/lib/Makefile b/arch/arm/lib/Makefile > > > index 6d2ba454f25b..8e4fe6421dd2 100644 > > > --- a/arch/arm/lib/Makefile > > > +++ b/arch/arm/lib/Makefile > > > @@ -43,8 +43,10 @@ endif > > > $(obj)/csumpartialcopy.o: $(obj)/csumpartialcopygeneric.S > > > $(obj)/csumpartialcopyuser.o: $(obj)/csumpartialcopygeneric.S > > > > > > +ifdef CONFIG_CC_IS_CLANG > > > ifeq ($(CONFIG_KERNEL_MODE_NEON),y) > > > NEON_FLAGS := -march=armv7-a -mfloat-abi=softfp -mfpu=neon > > > CFLAGS_xor-neon.o += $(NEON_FLAGS) > > > obj-$(CONFIG_XOR_BLOCKS) += xor-neon.o > > > endif > > > +endif > > > > Nevermind, this does not actually work. Just turning off the warning > > is probably best then, as actually disabling this code would still > > be invasive not do much beyond saving a little bit of kernel .text size. > > Ok, if it triggers again, and I get annoyed, I'll write a patch, > otherwise I'll just leave it alone unless someone else wants to send it > to me... The patch is trivial, if your idea is just to remove the #warning, right? Might as well just do it now and get it over with. Jason