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=-7.1 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_GIT 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 85256C433FE for ; Wed, 15 Jul 2020 08:27:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 62C0C206D5 for ; Wed, 15 Jul 2020 08:27:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Y7XBEzNJ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729679AbgGOI0k (ORCPT ); Wed, 15 Jul 2020 04:26:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728760AbgGOI0k (ORCPT ); Wed, 15 Jul 2020 04:26:40 -0400 Received: from mail-wr1-x443.google.com (mail-wr1-x443.google.com [IPv6:2a00:1450:4864:20::443]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A025DC08C5C1 for ; Wed, 15 Jul 2020 01:26:39 -0700 (PDT) Received: by mail-wr1-x443.google.com with SMTP id j4so1437446wrp.10 for ; Wed, 15 Jul 2020 01:26:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=BobjFLO4jAQDqgFYhhcPSkxXTsZfQxwIQ+LKOwR6wxQ=; b=Y7XBEzNJjKc0Iuki0fXG/IizMD/riuqZahAKVS5ebLIzW5x2fZVTWpy6exLgM6WY7l MF9LP/7Xb73DNN2spvTOF9U36s88+O3xtWMOpIrpF6Sfgc6j8e7zmWpbIi/9xhjsLvTN bj2xzlqQnQVI1Z1Lxz4/XkyLus0x8gaJZGHsyxNwKzOK2WqczCwK17WtLXmLVOLbx18H XCI7GnBRBA9oT6RsfcnuGN0ieJqplA8sZb+RI6WQ9nCptOpGfXGMqYhszYvn5o/NwNuZ UERu0D4MChT9C/fh+6wACJzJYspQllNfLiFilJvDcQnAJPp0/4qiGdv3Z94HEh1VkFTk 57Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=BobjFLO4jAQDqgFYhhcPSkxXTsZfQxwIQ+LKOwR6wxQ=; b=oKPbxtBRyV/vHDzx95YDJBkElcsguDMTA77/W3T3oxb/1X0l2opz0BIQj+2PB0VcFH s8Yx9MUzFkNV2zt7TSAAhoImPvMrUG80EgwJZqtDWBcqxmhdeEdS8N0YXC0fSUahXOpb 7juVZbDdiUqdDXuKhd9MIEhUtjEwESQfW6b98NtrviAghhlBSGwSeMZwVkB7WTpLpihR nFd278AJyn7m8SNst5NEMzgTIT+H9EqaRZBhG2hiPlW+mOS5XAphKX5IgiSuPH9OEr7Q BhwAPNRFczQR1xREY3TtmQDL933z4eSktNbu18374uZyHTlXjwd+AlOOlKlxVihcLh8Z PxCg== X-Gm-Message-State: AOAM532EQ6mP8XP5Pxa/BEk4HaWNGxdZI2OO8nfgZQkFo+Y2wV1BEQG/ XLW7lLY3zYynzubyIcd2e3dOng== X-Google-Smtp-Source: ABdhPJxavdVbilJtal4t/mMwWHDIMZMCfoDSecxBHUP8XJKJCPrqVA0w2Y2RAT0AGordCCwSHDd0xA== X-Received: by 2002:a05:6000:86:: with SMTP id m6mr9906018wrx.173.1594801598417; Wed, 15 Jul 2020 01:26:38 -0700 (PDT) Received: from localhost.localdomain ([2.31.163.61]) by smtp.gmail.com with ESMTPSA id h13sm2400361wml.42.2020.07.15.01.26.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jul 2020 01:26:37 -0700 (PDT) From: Lee Jones To: rjw@rjwysocki.net, viresh.kumar@linaro.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Lee Jones Subject: [PATCH v2 00/13] Rid W=1 warnings in CPUFreq Date: Wed, 15 Jul 2020 09:26:21 +0100 Message-Id: <20200715082634.3024816-1-lee.jones@linaro.org> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org 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. Hurrah! Changelog v1 => v2: - Collect *-bys - Use __maybe_unused instead of removing device IDs - Use __always_unused instead of using unused variables - Include architecture header instead of creating new include file Lee Jones (13): cpufreq: freq_table: Demote obvious misuse of kerneldoc to standard comment blocks cpufreq: cpufreq: Demote lots of function headers unworthy of kerneldoc status cpufreq: cpufreq_governor: Demote store_sampling_rate() header to standard comment block cpufreq: sti-cpufreq: Fix some formatting and misspelling issues cpufreq: pasemi: Include header file for {check,restore}_astate prototypes cpufreq: powernv-cpufreq: Functions only used in call-backs should be static cpufreq: powernv-cpufreq: Fix a bunch of kerneldoc related issues cpufreq: acpi-cpufreq: Mark 'dummy' variable as __always_unused cpufreq: acpi-cpufreq: Mark sometimes used ID structs as __maybe_unused cpufreq: powernow-k8: Mark 'hi' and 'lo' dummy variables as __always_unused cpufreq: pcc-cpufreq: Mark sometimes used ID structs as __maybe_unused cpufreq: intel_pstate: Supply struct attribute description for get_aperf_mperf_shift() cpufreq: amd_freq_sensitivity: Mark sometimes used ID structs as __maybe_unused drivers/cpufreq/acpi-cpufreq.c | 8 +++---- drivers/cpufreq/amd_freq_sensitivity.c | 2 +- drivers/cpufreq/cpufreq.c | 32 ++++++++++++++------------ drivers/cpufreq/cpufreq_governor.c | 2 +- drivers/cpufreq/freq_table.c | 6 ++--- drivers/cpufreq/intel_pstate.c | 2 ++ drivers/cpufreq/pasemi-cpufreq.c | 2 ++ drivers/cpufreq/pcc-cpufreq.c | 2 +- drivers/cpufreq/powernow-k8.c | 4 ++-- drivers/cpufreq/powernv-cpufreq.c | 15 ++++++------ drivers/cpufreq/sti-cpufreq.c | 8 +++---- 11 files changed, 45 insertions(+), 38 deletions(-) -- 2.25.1