linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Rob Clark <robdclark@gmail.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 3520/7405] drivers/gpu/drm/msm/msm_gem.c:624:34: error: implicit declaration of function 'vmap'; did you mean 'kmap'?
Date: Wed, 13 Oct 2021 14:53:19 +0200	[thread overview]
Message-ID: <74b093da-807e-cf1a-be26-cce826b9f7c0@amd.com> (raw)
In-Reply-To: <20211012160335.GJ2688930@ziepe.ca>

Am 12.10.21 um 18:03 schrieb Jason Gunthorpe:
> On Tue, Oct 12, 2021 at 09:03:04AM -0700, Rob Clark wrote:
>> Hmm, not seeing an easy (ie. `dnf install ..`) way to get a parisc
>> toolchain.. but I guess there isn't a lot of value in compile testing
>> on parisc, so maybe we can just limit the archs that we support
>> compile-testing on?
> tuxmake has a cross compile docker container available
>
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2FLinaro%2Ftuxmake&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7C838070858d51422ce24f08d98d99d9e9%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637696514201426415%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=cJ1stGW2iYQTvzEfpJ5S4OXFjHZ%2BGdr51DrFyn43lD8%3D&amp;reserved=0

I already figured out what's wrong here. parisc is a !MMU platform.

If nobody beats me I'm going to fix up the Kconfig dependencies as soon 
as my cold gets better and I'm back from sick leave.

Christian.

>
> Jason



      reply	other threads:[~2021-10-13 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 20:27 kernel test robot
2021-10-12  7:12 ` Christian König
2021-10-12 16:03   ` Rob Clark
2021-10-12 16:03     ` Jason Gunthorpe
2021-10-13 12:53       ` Christian König [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=74b093da-807e-cf1a-be26-cce826b9f7c0@amd.com \
    --to=christian.koenig@amd.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-mm@kvack.org \
    --cc=robdclark@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox