From: kernel test robot <lkp@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: kbuild-all@lists.01.org, "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
linaro-mm-sig@lists.linaro.org,
"David Stevens" <stevensd@chromium.org>,
"Christian König" <christian.koenig@amd.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] drm-buf: Add debug option
Date: Fri, 15 Jan 2021 23:36:16 +0800 [thread overview]
Message-ID: <202101152349.On5G28nD-lkp@intel.com> (raw)
In-Reply-To: <20210115130219.3915789-1-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 2732 bytes --]
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on next-20210115]
[also build test WARNING on v5.11-rc3]
[cannot apply to tegra-drm/drm/tegra/for-next linus/master v5.11-rc3 v5.11-rc2 v5.11-rc1]
[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]
url: https://github.com/0day-ci/linux/commits/Daniel-Vetter/drm-buf-Add-debug-option/20210115-210650
base: b3a3cbdec55b090d22a09f75efb7c7d34cb97f25
config: i386-randconfig-a012-20210115 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/a0f2603f574f0a1aedd7719cbb47b807796d2367
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Daniel-Vetter/drm-buf-Add-debug-option/20210115-210650
git checkout a0f2603f574f0a1aedd7719cbb47b807796d2367
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/dma-buf/dma-buf.c: In function '__map_dma_buf':
>> drivers/dma-buf/dma-buf.c:676:5: warning: "CONFIG_DMABUF_DEBUG" is not defined, evaluates to 0 [-Wundef]
676 | #if CONFIG_DMABUF_DEBUG
| ^~~~~~~~~~~~~~~~~~~
drivers/dma-buf/dma-buf.c: In function '__unmap_dma_buf':
drivers/dma-buf/dma-buf.c:816:5: warning: "CONFIG_DMABUF_DEBUG" is not defined, evaluates to 0 [-Wundef]
816 | #if CONFIG_DMABUF_DEBUG
| ^~~~~~~~~~~~~~~~~~~
vim +/CONFIG_DMABUF_DEBUG +676 drivers/dma-buf/dma-buf.c
668
669 static struct sg_table * __map_dma_buf(struct dma_buf_attachment *attach,
670 enum dma_data_direction direction)
671 {
672 struct sg_table *sg_table;
673
674 sg_table = attach->dmabuf->ops->map_dma_buf(attach, direction);
675
> 676 #if CONFIG_DMABUF_DEBUG
677 if (sg_table) {
678 int i;
679 struct scatterlist *sg;
680
681 /* To catch abuse of the underlying struct page by importers mix
682 * up the bits, but take care to preserve the low SG_ bits to
683 * not corrupt the sgt. The mixing is undone in __unmap_dma_buf
684 * before passing the sgt back to the exporter. */
685 for_each_sgtable_sg(sg_table, sg, i)
686 sg->page_link ^= ~0xffUL;
687 }
688 #endif
689
690 return sg_table;
691 }
692
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29077 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-01-15 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 13:02 [PATCH] drm-buf: Add debug option Daniel Vetter
2021-01-15 13:09 ` [Linaro-mm-sig] " Christian König
2021-01-15 13:22 ` Daniel Vetter
2021-01-15 13:24 ` Christian König
2021-01-15 15:36 ` kernel test robot [this message]
2021-01-15 15:50 ` [PATCH] dma-buf: " Daniel Vetter
2021-01-15 15:52 ` Daniel Vetter
2021-01-15 15:59 ` Chris Wilson
2021-01-15 16:20 ` Christian König
2021-01-15 16:47 ` Daniel Vetter
2021-01-15 18:52 ` Christian König
2021-01-18 13:27 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2021-01-13 14:06 [PATCH] drm-buf: " Daniel Vetter
2021-02-17 3:30 ` John Stultz
2021-02-17 3:34 ` John Stultz
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=202101152349.On5G28nD-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=stevensd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).