From: kernel test robot <lkp@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] drm/doc/rfc: Remove Xe's pre-merge plan
Date: Thu, 11 Jan 2024 22:53:09 +0800 [thread overview]
Message-ID: <202401112223.WHZuZo0K-lkp@intel.com> (raw)
In-Reply-To: <20240110190427.63095-1-rodrigo.vivi@intel.com>
Hi Rodrigo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next next-20240111]
[cannot apply to drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.7]
[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/Rodrigo-Vivi/drm-doc-rfc-Remove-Xe-s-pre-merge-plan/20240111-030712
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20240110190427.63095-1-rodrigo.vivi%40intel.com
patch subject: [PATCH] drm/doc/rfc: Remove Xe's pre-merge plan
reproduce: (https://download.01.org/0day-ci/archive/20240111/202401112223.WHZuZo0K-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/202401112223.WHZuZo0K-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/rfc/index.rst:35: WARNING: toctree contains reference to nonexisting document 'gpu/rfc/xe'
vim +35 Documentation/gpu/rfc/index.rst
ece91c882dee5f Niranjana Vishwanathapura 2022-06-30 32
ece91c882dee5f Niranjana Vishwanathapura 2022-06-30 33 i915_vm_bind.rst
40aeab044a352b Rodrigo Vivi 2023-04-19 34
40aeab044a352b Rodrigo Vivi 2023-04-19 @35 .. toctree::
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-01-11 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 19:04 [PATCH] drm/doc/rfc: Remove Xe's pre-merge plan Rodrigo Vivi
2024-01-10 19:04 ` Rodrigo Vivi
2024-01-10 20:07 ` Lucas De Marchi
2024-01-10 20:28 ` Rodrigo Vivi
2024-01-11 0:09 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-01-11 14:53 ` 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=202401112223.WHZuZo0K-lkp@intel.com \
--to=lkp@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.