From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [RFC v2 1/2] cpuidle: Extract IPI based and timer based wakeup latency from idle states
Date: Fri, 02 Apr 2021 17:03:06 +0800 [thread overview]
Message-ID: <202104021627.qFtgFvAz-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <20210401114504.13466-2-psampat@linux.ibm.com>
References: <20210401114504.13466-2-psampat@linux.ibm.com>
TO: Pratik Rajesh Sampat <psampat@linux.ibm.com>
Hi Pratik,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on kselftest/next]
[also build test WARNING on pm/linux-next linus/master daniel.lezcano/clockevents/next v5.12-rc5 next-20210401]
[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]
url: https://github.com/0day-ci/linux/commits/Pratik-Rajesh-Sampat/cpuidle-Extract-IPI-based-and-timer-based-wakeup-latency-from-idle-states/20210402-015842
base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
:::::: branch date: 15 hours ago
:::::: commit date: 15 hours ago
config: i386-allmodconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
cocci warnings: (new ones prefixed by >>)
>> drivers/cpuidle/test-cpuidle_latency.c:95:0-23: WARNING: ipi_ops should be defined with DEFINE_DEBUGFS_ATTRIBUTE
>> drivers/cpuidle/test-cpuidle_latency.c:108:0-23: WARNING: timeout_ops should be defined with DEFINE_DEBUGFS_ATTRIBUTE
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65514 bytes --]
next reply other threads:[~2021-04-02 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 9:03 kernel test robot [this message]
2021-04-02 9:03 ` [PATCH] cpuidle: fix debugfs_simple_attr.cocci warnings kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-04-01 11:45 [RFC v2 0/2] CPU-Idle latency selftest framework Pratik Rajesh Sampat
2021-04-01 11:45 ` [RFC v2 1/2] cpuidle: Extract IPI based and timer based wakeup latency from idle states Pratik Rajesh Sampat
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=202104021627.qFtgFvAz-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.