From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH V3 1/8] cxl/mem: Read, trace, and clear events on driver load
Date: Fri, 9 Dec 2022 15:14:54 +0800 [thread overview]
Message-ID: <202212091529.KGJtfbLV-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20221208052115.800170-2-ira.weiny@intel.com>
References: <20221208052115.800170-2-ira.weiny@intel.com>
TO: ira.weiny@intel.com
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on acb704099642bc822ef2aed223a0b8db1f7ea76e]
url: https://github.com/intel-lab-lkp/linux/commits/ira-weiny-intel-com/CXL-Process-event-logs/20221208-132333
base: acb704099642bc822ef2aed223a0b8db1f7ea76e
patch link: https://lore.kernel.org/r/20221208052115.800170-2-ira.weiny%40intel.com
patch subject: [PATCH V3 1/8] cxl/mem: Read, trace, and clear events on driver load
:::::: branch date: 26 hours ago
:::::: commit date: 26 hours ago
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> drivers/cxl/core/trace.h: linux/tracepoint.h is included more than once.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-12-09 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 7:14 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-08 5:21 [PATCH V3 0/8] CXL: Process event logs ira.weiny
2022-12-08 5:21 ` [PATCH V3 1/8] cxl/mem: Read, trace, and clear events on driver load ira.weiny
2022-12-09 17:56 ` Dan Williams
2022-12-09 21:00 ` Ira Weiny
2022-12-09 22:33 ` Dan Williams
2022-12-09 23:34 ` Ira Weiny
2022-12-12 17:58 ` Jonathan Cameron
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=202212091529.KGJtfbLV-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.