From: kernel test robot <lkp@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
airlied@gmail.com, daniel.vetter@ffwll.ch
Cc: Jani Nikula <jani.nikula@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Updates to Intel DRM
Date: Thu, 14 Dec 2023 19:34:31 +0800 [thread overview]
Message-ID: <202312141902.3smgOmnr-lkp@intel.com> (raw)
In-Reply-To: <20231213160915.1414733-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-tip/drm-tip linus/master v6.7-rc5 next-20231214]
[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/MAINTAINERS-Updates-to-Intel-DRM/20231214-001056
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20231213160915.1414733-1-rodrigo.vivi%40intel.com
patch subject: [PATCH] MAINTAINERS: Updates to Intel DRM
reproduce: (https://download.01.org/0day-ci/archive/20231214/202312141902.3smgOmnr-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/202312141902.3smgOmnr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: MAINTAINERS references a file that doesn't exist: Documentation/ABI/testing/sysfs-driver-intel-xe-hwmon
>> Warning: MAINTAINERS references a file that doesn't exist: Documentation/gpu/xe/
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-14 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 16:09 [PATCH] MAINTAINERS: Updates to Intel DRM Rodrigo Vivi
2023-12-13 16:12 ` ✓ CI.Patch_applied: success for " Patchwork
2023-12-13 16:12 ` ✗ CI.checkpatch: warning " Patchwork
2023-12-13 16:13 ` ✓ CI.KUnit: success " Patchwork
2023-12-13 16:21 ` ✓ CI.Build: " Patchwork
2023-12-13 16:21 ` ✓ CI.Hooks: " Patchwork
2023-12-13 16:22 ` ✓ CI.checksparse: " Patchwork
2023-12-13 16:59 ` ✓ CI.BAT: " Patchwork
2023-12-14 11:34 ` 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=202312141902.3smgOmnr-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox