mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Oza Pawandeep <quic_poza@quicinc.com>,
	sudeep.holla@arm.com, catalin.marinas@arm.com, will@kernel.org,
	rafael@kernel.org, lenb@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Oza Pawandeep <quic_poza@quicinc.com>
Subject: Re: [PATCH v6] cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer
Date: Fri, 15 Sep 2023 11:39:16 +0800	[thread overview]
Message-ID: <202309151138.69mFCPtW-lkp@intel.com> (raw)
In-Reply-To: <20230914184840.649412-1-quic_poza@quicinc.com>

Hi Oza,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc1 next-20230915]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Oza-Pawandeep/cpuidle-ACPI-Evaluate-LPI-arch_flags-for-broadcast-timer/20230915-025307
base:   linus/master
patch link:    https://lore.kernel.org/r/20230914184840.649412-1-quic_poza%40quicinc.com
patch subject: [PATCH v6] cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20230915/202309151138.69mFCPtW-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230915/202309151138.69mFCPtW-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309151138.69mFCPtW-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from arch/arm64/kernel/setup.c:36:
>> arch/arm64/include/asm/acpi.h:60: warning: "arch_update_idle_state_flags" redefined
      60 | #define arch_update_idle_state_flags _arch_update_idle_state_flags
         | 
   In file included from arch/arm64/kernel/setup.c:9:
   include/linux/acpi.h:1484: note: this is the location of the previous definition
    1484 | #define arch_update_idle_state_flags(af, sf)    do {} while (0)
         | 


vim +/arch_update_idle_state_flags +60 arch/arm64/include/asm/acpi.h

    53	
    54	static __always_inline void _arch_update_idle_state_flags(u32 arch_flags,
    55								unsigned int *sflags)
    56	{
    57		if (arch_flags & CPUIDLE_CORE_CTXT)
    58			*sflags |= CPUIDLE_FLAG_TIMER_STOP;
    59	}
  > 60	#define arch_update_idle_state_flags _arch_update_idle_state_flags
    61	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2023-09-15  3:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 18:48 Oza Pawandeep
2023-09-15  3:39 ` kernel test robot [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=202309151138.69mFCPtW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=quic_poza@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®