From: kernel test robot <lkp@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
linux-doc@vger.kernel.org, intel-xe@lists.freedesktop.org,
oe-kbuild-all@lists.linux.dev
Subject: [Intel-xe] [drm-xe:drm-xe-next 964/1394] htmldocs: Documentation/gpu/drm-mm:552: ./drivers/gpu/drm/scheduler/sched_main.c:50: WARNING: Enumerated list ends without a blank line; unexpected unindent.
Date: Mon, 30 Oct 2023 06:37:05 +0800 [thread overview]
Message-ID: <202310300643.q7ugWxc9-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head: f24c46200dc8fad700f51106e678d68d38496860
commit: 0dceb0dede50613712a065d627443f4c182e6e2c [964/1394] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
reproduce: (https://download.01.org/0day-ci/archive/20231030/202310300643.q7ugWxc9-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/202310300643.q7ugWxc9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/drm-mm:552: ./drivers/gpu/drm/scheduler/sched_main.c:50: WARNING: Enumerated list ends without a blank line; unexpected unindent.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, intel-xe@lists.freedesktop.org,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
linux-doc@vger.kernel.org
Subject: [drm-xe:drm-xe-next 964/1394] htmldocs: Documentation/gpu/drm-mm:552: ./drivers/gpu/drm/scheduler/sched_main.c:50: WARNING: Enumerated list ends without a blank line; unexpected unindent.
Date: Mon, 30 Oct 2023 06:37:05 +0800 [thread overview]
Message-ID: <202310300643.q7ugWxc9-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head: f24c46200dc8fad700f51106e678d68d38496860
commit: 0dceb0dede50613712a065d627443f4c182e6e2c [964/1394] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
reproduce: (https://download.01.org/0day-ci/archive/20231030/202310300643.q7ugWxc9-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/202310300643.q7ugWxc9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/drm-mm:552: ./drivers/gpu/drm/scheduler/sched_main.c:50: WARNING: Enumerated list ends without a blank line; unexpected unindent.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-29 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 22:37 kernel test robot [this message]
2023-10-29 22:37 ` [drm-xe:drm-xe-next 964/1394] htmldocs: Documentation/gpu/drm-mm:552: ./drivers/gpu/drm/scheduler/sched_main.c:50: WARNING: Enumerated list ends without a blank line; unexpected unindent 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=202310300643.q7ugWxc9-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
/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.