From: Thomas Zimmermann <tzimmermann@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>, kernel test robot <lkp@intel.com>
Cc: dri-devel@lists.freedesktop.org, kbuild-all@lists.01.org,
linux-aspeed@lists.ozlabs.org, airlied@linux.ie,
naresh.kamboju@linaro.org, llvm@lists.linux.dev,
linux-mips@vger.kernel.org, noralf@tronnes.org,
marcel@ziswiler.com
Subject: Re: [PATCH 2/2] drm: Remove CONFIG_DRM_KMS_CMA_HELPER option
Date: Sat, 6 Nov 2021 20:49:33 +0100 [thread overview]
Message-ID: <584f7943-f16c-dc37-5005-e1b732509a15@suse.de> (raw)
In-Reply-To: <YYVw70934dYhyGVZ@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 3076 bytes --]
Hi
Am 05.11.21 um 18:59 schrieb Daniel Vetter:
> On Mon, Nov 01, 2021 at 11:59:15PM +0800, kernel test robot wrote:
>> Hi Thomas,
>>
>> I love your patch! Yet something to improve:
>>
>> [auto build test ERROR on next-20211029]
>> [cannot apply to drm/drm-next shawnguo/for-next pinchartl-media/drm/du/next v5.15 v5.15-rc7 v5.15-rc6 v5.15]
>> [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/Thomas-Zimmermann/drm-Small-CMA-cleanups/20211101-161911
>> base: bdcc9f6a568275aed4cc32fd2312432d2ff1b704
>> config: x86_64-randconfig-a004-20211101 (attached as .config)
>> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 82ed106567063ea269c6d5669278b733e173a42f)
>> reproduce (this is a W=1 build):
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # https://github.com/0day-ci/linux/commit/c3c7ec5f9ccd90e78f0f2d3143505db4060bbf17
>> git remote add linux-review https://github.com/0day-ci/linux
>> git fetch --no-tags linux-review Thomas-Zimmermann/drm-Small-CMA-cleanups/20211101-161911
>> git checkout c3c7ec5f9ccd90e78f0f2d3143505db4060bbf17
>> # save the attached .config to linux build tree
>> mkdir build_dir
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>, old ones prefixed by <<):
>>
>>>> ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vmap from namespace DMA_BUF, but does not import it.
>>>> ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vunmap from namespace DMA_BUF, but does not import it.
>
> I guess this is simply because kbuild tests on top of linux-next, where
> the namespacing is a bit funny. We might need a fixup when we backmerge.
>
> Either way this looks like a good simplification to me, on the series:
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Thanks a lot. We fixed the namespace problem in 675053115e4e ("drm:
import DMA_BUF module namespace"). But the dma-buf namespace patch is
not in drm-misc trees. Given how widely used the dma-buf interface is,
the backmerge will indeed cause some trouble.
I meanwhile sent out the patchset with a base commit. Kernel CI will
hopefully succeed now.
Best regards
Thomas
>
>>
>> ---
>> 0-DAY CI Kernel Test Service, Intel Corporation
>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2021-11-06 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 8:17 [PATCH 0/2] drm: Small CMA cleanups Thomas Zimmermann
2021-11-01 8:17 ` [PATCH 1/2] drm/mipi-dbi: Remove dependency on GEM CMA helper library Thomas Zimmermann
2021-11-01 8:17 ` [PATCH 2/2] drm: Remove CONFIG_DRM_KMS_CMA_HELPER option Thomas Zimmermann
2021-11-01 15:59 ` kernel test robot
2021-11-05 17:59 ` Daniel Vetter
2021-11-06 19:49 ` Thomas Zimmermann [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=584f7943-f16c-dc37-5005-e1b732509a15@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=marcel@ziswiler.com \
--cc=naresh.kamboju@linaro.org \
--cc=noralf@tronnes.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