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=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 590DDC433DF for ; Wed, 15 Jul 2020 03:36:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2BC232075B for ; Wed, 15 Jul 2020 03:36:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Mq1a22iM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728518AbgGODgb (ORCPT ); Tue, 14 Jul 2020 23:36:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726648AbgGODga (ORCPT ); Tue, 14 Jul 2020 23:36:30 -0400 Received: from mail-pf1-x443.google.com (mail-pf1-x443.google.com [IPv6:2607:f8b0:4864:20::443]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B7B82C061794 for ; Tue, 14 Jul 2020 20:36:30 -0700 (PDT) Received: by mail-pf1-x443.google.com with SMTP id s26so1295875pfm.4 for ; Tue, 14 Jul 2020 20:36:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Wo4NFzdUiw6uJIzUDiz1BlvrT/9thiObvUTasK+LFJQ=; b=Mq1a22iMCVQmgzxOV0p0g+z9f6rKXO6mZiH6yQC84D5gxUZna9mVPfEGlQlm4ODD4s jvEcnb70QVoapMd8KwRbccqaKJCCIvOC3TlbYRSlR35kKKN9MSD12iMV7tzjfnh0jhxY 1e/ZT5ntIMkVbQZrEt9sgT6hauP/RZtbcjpqij4a2lVbIB4rs7f6XIrepinp36VDp/8/ ayHDNS59IXPBQ+4KCBhdaDOpiZSkee50rFHZ3cN5xPaMwjY0heHMsIWgPehAtKfe8cTe pWU+sCF3m+71zjIm6CYlZT9jftXoi1Y/3N2Cni8Ee4NjlK2z8pqO0iWO6rR4mRTdyC9a PA4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Wo4NFzdUiw6uJIzUDiz1BlvrT/9thiObvUTasK+LFJQ=; b=kRZMDiQx5l8/IjlZ1DWLWwdh5ioscRSPh9qNh8DmQrEdYPlPyiy83YNE9PMJWOi1gl h91LEAMoMj7zO3QIGoYSGZKnxNue9HWjfuBcPELmXwbFuDuMbVK0IkdD6LFsQ1qL4PV8 XRGW28yxiqbpFfSAkPdMM5u06hJjMQjUb/7g+qGJNNmhwSA2WrSSA3HFRtMKdtnQ/3jC BX2P7IkURvxwi+SjQ/D0MuREr04GRz3QCVL4MYejNzzAEMMSR+CCPU2ee8LqpYSHqUqA ICiC/ZBs2g1Zuj1UzCzqFxUGIL/QqZH4LmzL3oWNejcXFGOOPFwl5xb556wkgIb4omiC j6uA== X-Gm-Message-State: AOAM5312g3z4UzBlzj6mxN2ONIffI1NBobAeh+X7Byfaa3dSpO+vQYmI p7YKOXgqEW5/z6WEL96F9U9mGg== X-Google-Smtp-Source: ABdhPJx0CEZPVwHRb6DRG98OrDg97SD6ru4U8kBXKcnC8XCCUtODi6z6J8bdIefYHU1pjE+nyl0sUQ== X-Received: by 2002:a63:e60b:: with SMTP id g11mr6368821pgh.188.1594784190122; Tue, 14 Jul 2020 20:36:30 -0700 (PDT) Received: from localhost ([122.172.34.142]) by smtp.gmail.com with ESMTPSA id nh14sm424492pjb.4.2020.07.14.20.36.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jul 2020 20:36:29 -0700 (PDT) Date: Wed, 15 Jul 2020 09:06:27 +0530 From: Viresh Kumar To: Lee Jones Cc: rjw@rjwysocki.net, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH 00/13] Rid W=1 warnings in CPUFreq Message-ID: <20200715033627.k6ardlhm3z3w65xw@vireshk-i7> References: <20200714145049.2496163-1-lee.jones@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200714145049.2496163-1-lee.jones@linaro.org> User-Agent: NeoMutt/20180716-391-311a52 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On 14-07-20, 15:50, Lee Jones wrote: > This set is part of a larger effort attempting to clean-up W=1 > kernel builds, which are currently overwhelmingly riddled with > niggly little warnings. > > After these patches are applied, the build system no longer > complains about any W=0 nor W=1 level warnings in drivers/cpufreq. And you need to rebase this stuff of pm/linux-next, as there are some changes in cpufreq.c there. -- viresh