From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, Oak Zeng <oak.zeng@intel.com>,
Danilo Krummrich <dakr@redhat.com>,
dri-devel@lists.freedesktop.org, oe-kbuild-all@lists.linux.dev,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-xe] [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document
Date: Sun, 25 Jun 2023 18:00:08 +0800 [thread overview]
Message-ID: <202306251715.VhtKaEVg-lkp@intel.com> (raw)
In-Reply-To: <20230621100435.54425-1-thomas.hellstrom@linux.intel.com>
Hi Thomas,
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-tip/drm-tip next-20230623]
[cannot apply to linus/master v6.4-rc7]
[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/Thomas-Hellstr-m/Documentation-gpu-Add-a-VM_BIND-async-draft-document/20230621-180712
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230621100435.54425-1-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document
reproduce: (https://download.01.org/0day-ci/archive/20230625/202306251715.VhtKaEVg-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/202306251715.VhtKaEVg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/drm-vm-bind-async.rst:95: WARNING: Title underline too short.
>> Documentation/gpu/drm-vm-bind-async.rst: WARNING: document isn't included in any toctree
vim +95 Documentation/gpu/drm-vm-bind-async.rst
93
94 Multi-operation VM_BIND IOCTL error handling and interrupts
> 95 ========================================
96
--
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: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
linux-kernel@vger.kernel.org, "Oak Zeng" <oak.zeng@intel.com>,
"Danilo Krummrich" <dakr@redhat.com>,
dri-devel@lists.freedesktop.org,
"Nirmoy Das" <nirmoy.das@intel.com>
Subject: Re: [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document
Date: Sun, 25 Jun 2023 18:00:08 +0800 [thread overview]
Message-ID: <202306251715.VhtKaEVg-lkp@intel.com> (raw)
In-Reply-To: <20230621100435.54425-1-thomas.hellstrom@linux.intel.com>
Hi Thomas,
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-tip/drm-tip next-20230623]
[cannot apply to linus/master v6.4-rc7]
[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/Thomas-Hellstr-m/Documentation-gpu-Add-a-VM_BIND-async-draft-document/20230621-180712
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230621100435.54425-1-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document
reproduce: (https://download.01.org/0day-ci/archive/20230625/202306251715.VhtKaEVg-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/202306251715.VhtKaEVg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/drm-vm-bind-async.rst:95: WARNING: Title underline too short.
>> Documentation/gpu/drm-vm-bind-async.rst: WARNING: document isn't included in any toctree
vim +95 Documentation/gpu/drm-vm-bind-async.rst
93
94 Multi-operation VM_BIND IOCTL error handling and interrupts
> 95 ========================================
96
--
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: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
linux-kernel@vger.kernel.org, "Oak Zeng" <oak.zeng@intel.com>,
"Danilo Krummrich" <dakr@redhat.com>,
dri-devel@lists.freedesktop.org, oe-kbuild-all@lists.linux.dev,
"Nirmoy Das" <nirmoy.das@intel.com>
Subject: Re: [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document
Date: Sun, 25 Jun 2023 18:00:08 +0800 [thread overview]
Message-ID: <202306251715.VhtKaEVg-lkp@intel.com> (raw)
In-Reply-To: <20230621100435.54425-1-thomas.hellstrom@linux.intel.com>
Hi Thomas,
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-tip/drm-tip next-20230623]
[cannot apply to linus/master v6.4-rc7]
[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/Thomas-Hellstr-m/Documentation-gpu-Add-a-VM_BIND-async-draft-document/20230621-180712
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230621100435.54425-1-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document
reproduce: (https://download.01.org/0day-ci/archive/20230625/202306251715.VhtKaEVg-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/202306251715.VhtKaEVg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/drm-vm-bind-async.rst:95: WARNING: Title underline too short.
>> Documentation/gpu/drm-vm-bind-async.rst: WARNING: document isn't included in any toctree
vim +95 Documentation/gpu/drm-vm-bind-async.rst
93
94 Multi-operation VM_BIND IOCTL error handling and interrupts
> 95 ========================================
96
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-25 10:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 10:04 [Intel-xe] [PATCH v2] Documentation/gpu: Add a VM_BIND async draft document Thomas Hellström
2023-06-21 10:04 ` Thomas Hellström
2023-06-21 10:04 ` Thomas Hellström
2023-06-21 10:07 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-06-21 10:07 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-06-21 10:09 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-06-21 10:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-06-21 10:13 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-06-21 10:14 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-06-21 11:00 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-06-21 11:23 ` [Intel-xe] [PATCH v2] " Danilo Krummrich
2023-06-21 11:23 ` Danilo Krummrich
2023-06-21 11:23 ` Danilo Krummrich
2023-06-21 14:14 ` [Intel-xe] " Thomas Hellström
2023-06-21 14:14 ` Thomas Hellström
2023-06-21 14:14 ` Thomas Hellström
2023-06-25 10:00 ` kernel test robot [this message]
2023-06-25 10:00 ` kernel test robot
2023-06-25 10:00 ` 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=202306251715.VhtKaEVg-lkp@intel.com \
--to=lkp@intel.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nirmoy.das@intel.com \
--cc=oak.zeng@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.hellstrom@linux.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.