From: Ard Biesheuvel Subject: Re: [PATCH 1/5] crypto: arm/aes-ce - enable module autoloading based on CPU feature bits Date: Mon, 10 Sep 2018 09:01:56 +0200 Message-ID: References: <1495362220-30044-1-git-send-email-ard.biesheuvel@linaro.org> <1495362220-30044-2-git-send-email-ard.biesheuvel@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , linux-arm-kernel , Herbert Xu To: Stefan Agner Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Id: linux-crypto.vger.kernel.org On 10 September 2018 at 08:21, Stefan Agner wrote: > Hi Ard, > > On 21.05.2017 03:23, Ard Biesheuvel wrote: >> Make the module autoloadable by tying it to the CPU feature bit that >> describes whether the optional instructions it relies on are implemented >> by the current CPU. >> > > This leads to a compiler warning when compiling multi_v7_defconfig/ARM32 > using Clang 6.0.1: > > arch/arm/crypto/aes-ce-glue.c:450:1: warning: variable > 'cpu_feature_match_AES' is not needed and will not > be emitted [-Wunneeded-internal-declaration] > module_cpu_feature_match(AES, aes_init); > > ./include/linux/cpufeature.h:48:33: note: expanded from macro > 'module_cpu_feature_match' > static struct cpu_feature const cpu_feature_match_ ## x[] = \ > > :83:1: note: expanded from here > cpu_feature_match_AES > ^ > 1 warning generated. > > Do you happen to have an idea how to alleviate? > I guess this only happens for modules that are selected as builtin, and so MODULE_DEVICE_TABLE() resolves to nothing? Does this only occur for CPU features?