Re: linux-next: build failure after merge of the drm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: linux-next: build failure after merge of the drm tree
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 28 Sep 2020 08:04:27 +0200
Cc: Dave Airlie <airlied@xxxxxxxx>, DRI <dri-devel@xxxxxxxxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Paul Cercueil <paul@xxxxxxxxxxxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20200928135405.73404219@canb.auug.org.au>
References: <20200928135405.73404219@canb.auug.org.au>
User-agent: Mutt/1.5.17 (2007-11-01)

On Mon, Sep 28, 2020 at 01:54:05PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:

The driver needs to switch do dma_alloc_noncoherent + dma_sync_single*
like the other drivers converted in the dma tree.  Paul, let me know if
you have any questions.

Follow-Ups:
- Re: linux-next: build failure after merge of the drm tree
  - From: Paul Cercueil
- Re: linux-next: build failure after merge of the drm tree
  - From: Dave Airlie

References:
- linux-next: build failure after merge of the drm tree
  - From: Stephen Rothwell

Prev by Date: Re: [PATCH] ptp: add stub function for ptp_get_msgtype()
Next by Date: Re: linux-next: build failure after merge of the vfs tree
Previous by thread: linux-next: build failure after merge of the drm tree
Next by thread: Re: linux-next: build failure after merge of the drm tree
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Linux USB Development] [Yosemite News] [Linux SCSI]

Powered by Linux