public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: Marcel Ziswiler <marcel@ziswiler.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	open list <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Maxime Ripard <mripard@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH v2] drm: import DMA_BUF module namespace
Date: Sun, 31 Oct 2021 19:13:17 +0100	[thread overview]
Message-ID: <eadfa89d-1c39-be25-abaf-4150396e1024@suse.de> (raw)
In-Reply-To: <20211031132155.7dc972e8@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 1691 bytes --]

Hi

Am 31.10.21 um 03:21 schrieb Stephen Rothwell:
> Hi Thomas,
> 
> On Fri, 29 Oct 2021 20:51:52 +0200 Thomas Zimmermann <tzimmermann@suse.de> wrote:
>>
>> Am 27.10.21 um 23:25 schrieb Marcel Ziswiler:
>>> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>>>
>>> Today's -next fails building arm64 defconfig as follows:
>>>
>>> ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vunmap from
>>>    namespace DMA_BUF, but does not import it.
>>> ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vmap from
>>>    namespace DMA_BUF, but does not import it.
>>>
>>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>> Fixes: commit 4b2b5e142ff4 ("drm: Move GEM memory managers into modules")
>>> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>>
>> I added this fix into drm-misc-next. Thanks!
>>
>> However, I had to import linux-next while doing so. 'Git am' did a
>> 3-way merge, which may result in a conflict when the fix reaches
>> linux-next again. I also updated the commit description.
> 
> You cannot merge linux-next into any tree, sorry.  It rebases every day
> (and so do several of the included trees).

No no, don't worry. I meant 'import' as in 'git remote add linux-next'. 
I was actually complaining that the provided fix was not against a DRM tree.

Best regards
Thomas

> 
> Your fix patch should be sent to Greg KH and Arnd as the build failure
> is introduced in the char-misc tree.
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2021-10-31 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 21:25 [PATCH v2] drm: import DMA_BUF module namespace Marcel Ziswiler
2021-10-29 18:51 ` Thomas Zimmermann
2021-10-31  2:21   ` Stephen Rothwell
2021-10-31  3:30     ` Stephen Rothwell
2021-10-31 18:13     ` Thomas Zimmermann [this message]
2021-10-31 21:25       ` Stephen Rothwell

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=eadfa89d-1c39-be25-abaf-4150396e1024@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreyknvl@gmail.com \
    --cc=arnd@arndb.de \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft@linaro.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marcel@ziswiler.com \
    --cc=mripard@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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