From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kernel test robot <lkp@intel.com>,
linux-acpi@vger.kernel.org, devel@acpica.org,
linux-pm@vger.kernel.org
Subject: Re: [rafael-pm:bleeding-edge] BUILD SUCCESS 18e0452b740e01daf1abb498116ad89716bfd5bc
Date: Wed, 21 Feb 2024 14:21:52 +0000 [thread overview]
Message-ID: <08ab3e7b-c9af-4c07-bff9-1ae64f298eae@arm.com> (raw)
In-Reply-To: <202402211643.99kLO5dl-lkp@intel.com>
Hi Rafael,
On 2/21/24 08:16, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
> branch HEAD: 18e0452b740e01daf1abb498116ad89716bfd5bc Merge branch 'acpi-scan' into bleeding-edge
>
> Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> |-- arm64-defconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- arm64-randconfig-001-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- i386-allmodconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- i386-allyesconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- i386-buildonly-randconfig-006-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- i386-randconfig-015-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- i386-randconfig-141-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- mips-allyesconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- powerpc64-randconfig-002-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- powerpc64-randconfig-003-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- sparc64-randconfig-002-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> `-- x86_64-buildonly-randconfig-002-20240221
> |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> clang_recent_errors
> |-- i386-randconfig-014-20240221
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- riscv-allmodconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- riscv-allyesconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> |-- x86_64-allmodconfig
> | |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> | `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
> `-- x86_64-allyesconfig
> |-- kernel-power-energy_model.c:warning:Function-parameter-or-struct-member-nr_states-not-described-in-em_dev_compute_costs
> `-- kernel-power-energy_model.c:warning:variable-nr_states-set-but-not-used
>
> elapsed time: 726m
>
I have figured out the 2 places which trigger this. I'm going to send
a small patch to calm down those static checks.
Regards,
Lukasz
prev parent reply other threads:[~2024-02-21 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 8:16 [rafael-pm:bleeding-edge] BUILD SUCCESS 18e0452b740e01daf1abb498116ad89716bfd5bc kernel test robot
2024-02-21 14:21 ` Lukasz Luba [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08ab3e7b-c9af-4c07-bff9-1ae64f298eae@arm.com \
--to=lukasz.luba@arm.com \
--cc=devel@acpica.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox