Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp1447897pxv; Fri, 23 Jul 2021 08:32:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyL58TzibOrFcCOP18VFVX3iHNuwlGZxwjUH4wzu5eQtT7TEFHZH1oUB+73MklhKzr8bi5E X-Received: by 2002:a05:6402:5215:: with SMTP id s21mr6487231edd.356.1627054358741; Fri, 23 Jul 2021 08:32:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627054358; cv=none; d=google.com; s=arc-20160816; b=W+io0HMVj+wztyYWeCPz/1prWC5H/pzlQg7ovhyZ3QwPDqMjqG1UmQQgEf6xq9f58v Vw9yjjPN7tjcQqpyM2TRbfv5M8YykdAv/7aBC7XoGSDMVy3FcdDhvW0o/5zR7Z+pEsHs FW/w5RFmW9MHKJUwn9NZ+GFpAwKPh8jk8YAuG7S+z/sWZzE/8oAZop+MWWZUEHb5gTaA LegM904o584C3fKBj15ppJJEjMHLPR9JynU9PR5UsL2Z3d7jY5xsmse846rOAo5HQry3 LpbNFXvRprjfXybLwFYupjz4sJdBjpy3yXC5rQdL1JE67bXmSZcjFfwxl4+wQBTQgIDX CM1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=cyDblG0jWoL4GP0bQ1+MbSxzMK2F9PTMgl9Jw7jbjvo=; b=IPGd7G6xk4dMi0s34USQxzlDUKHjTjDEQK7IXZssTRSUw8ESVGYW7OgNH22+GjVYkK XFEBjsgE1ZETUgVR7Ok0lMAkDRSaZevftwLMRLCocDz/huPiWJfFfjlgBXmKSDDRyPJL Iw1oKtK06zFIoFKUFgdYQOGRZseCJpMCFuoGJPLshVFh/tuDVZ8XTkyP2f8nAQDSK5jb TKPHILDYX9qwyj+/sYSFlAICZu+58vw8A59gmA+DNVGMBOSezWaB5gGmFzJxeanHST6c nd66iqbciY8t81ivUdJ8z3KGMYfOSLrnsz1/ek3hcjfxxb+XFkxby3B9RHnPrq9tYPWR ul0Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lc6si711485ejc.720.2021.07.23.08.32.14; Fri, 23 Jul 2021 08:32:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235554AbhGWOq5 (ORCPT + 99 others); Fri, 23 Jul 2021 10:46:57 -0400 Received: from foss.arm.com ([217.140.110.172]:47428 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235501AbhGWOqd (ORCPT ); Fri, 23 Jul 2021 10:46:33 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2962112FC; Fri, 23 Jul 2021 08:27:07 -0700 (PDT) Received: from e113632-lin (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5B5D43F73D; Fri, 23 Jul 2021 08:27:06 -0700 (PDT) From: Valentin Schneider To: Arnd Bergmann , Ingo Molnar Cc: Arnd Bergmann , Peter Zijlstra , linux-kernel@vger.kernel.org Subject: Re: [PATCH] smpboot: remove duplicate inline keyword In-Reply-To: <20210723091618.1750551-1-arnd@kernel.org> References: <20210723091618.1750551-1-arnd@kernel.org> Date: Fri, 23 Jul 2021 16:27:01 +0100 Message-ID: <8735s5m4oq.mognet@arm.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 23/07/21 11:16, Arnd Bergmann wrote: > From: Arnd Bergmann > > 'static inline void __always_inline' is one more 'inline' than needed, > and it's in the wrong place as gcc points out when extra warnings > are enabled: > > kernel/smpboot.c:50:1: error: 'inline' is not at beginning of declaration [-Werror=old-style-declaration] > 50 | static inline void __always_inline idle_init(unsigned int cpu) > > Move it to the right place instead. > > Fixes: e9ba16e68cce ("smpboot: Mark idle_init() as __always_inlined to work around aggressive compiler un-inlining") > Signed-off-by: Arnd Bergmann Colin sent a similar fix at: http://lore.kernel.org/r/20210715164018.62712-1-colin.king@canonical.com Now AFAICT the incriminated patch is in tip/core/urgent and linux-next/master, but not in the current mainline. If so, this could be fixed up before it gets pulled.