From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.9-q-release 7904/9999] include/linux/delayacct.h: linux/slab.h is included more than once.
Date: Thu, 30 Jun 2022 16:34:16 +0800 [thread overview]
Message-ID: <202206301600.v3FEpwZS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
TO: Ammar Faizi <ammarfaizi2@gnuweeb.org>
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.9-q-release
head: 8c62b2bd034cfb52860b9e3f333b1ef587052af2
commit: 0f3e95cb46285a27db306d7a6e48fcf8a317b762 [7904/9999] UPSTREAM: sched/headers, delayacct: Move the 'struct task_delay_info' definition from <linux/sched.h> to <linux/delayacct.h>
:::::: branch date: 4 months ago
:::::: commit date: 3 years, 3 months ago
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.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 >>)
>> include/linux/delayacct.h: linux/slab.h is included more than once.
>> /kbuild/src/consumer/include/linux/delayacct.h: linux/sched.h is included more than once.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-06-30 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 8:34 kernel test robot [this message]
2022-08-20 1:05 [ammarfaizi2-block:google/android/kernel/common/android-4.9-q-release 7904/9999] include/linux/delayacct.h: linux/slab.h is included more than once kernel test robot
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=202206301600.v3FEpwZS-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.