public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Dmitry Osipenko <digetx@gmail•com>,
	Thierry Reding <treding@nvidia•com>,
	Christoph Hellwig <hch@lst•de>
Cc: linux-tegra@vger•kernel.org, linaro-kernel@lists•linaro.org,
	linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
	kernel-build-reports@lists•linaro.org
Subject: Re: next-20190206 build: 3 failures 22 warnings (next-20190206)
Date: Wed, 6 Feb 2019 18:24:31 +0000	[thread overview]
Message-ID: <20190206182431.GH17630@sirena.org.uk> (raw)
In-Reply-To: <E1grRJi-0002vu-FB@optimist>


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

On Wed, Feb 06, 2019 at 05:48:58PM +0000, Build bot for Mark Brown wrote:

Today's -next fails to build an arm64 defconfig and allmodconfig due to:

> ERROR: "dma_direct_free" [drivers/gpu/host1x/host1x.ko] undefined!
> ERROR: "dma_direct_alloc" [drivers/gpu/host1x/host1x.ko] undefined!

due to 7a0658caa44d01 (gpu: host1x: Use direct DMA with IOMMU API usage)
which adds usage of those non-exported functions.  Either the functions
need exporting, the driver needs to be built in or those functions can't
be used.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

           reply	other threads:[~2019-02-06 18:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <E1grRJi-0002vu-FB@optimist>]

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=20190206182431.GH17630@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=digetx@gmail$(echo .)com \
    --cc=hch@lst$(echo .)de \
    --cc=kernel-build-reports@lists$(echo .)linaro.org \
    --cc=linaro-kernel@lists$(echo .)linaro.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-tegra@vger$(echo .)kernel.org \
    --cc=treding@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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