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

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

Subject: Re: linux-next: build failure after merge of the rpmsg tree
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 22 Feb 2019 13:50:46 +0100
Cc: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Loic Pallardy <loic.pallardy@xxxxxx>
In-reply-to: <20190222161817.32e35462@canb.auug.org.au>
References: <20190222161817.32e35462@canb.auug.org.au>
User-agent: Mutt/1.5.17 (2007-11-01)

FYI, can I please get an explanation for the remoteproc changes?

We really should avoid adding new callers of dma_declare_coherent_memory,
which is a rather badly designed interface.

Follow-Ups:
- RE: linux-next: build failure after merge of the rpmsg tree
  - From: Loic PALLARDY

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

Prev by Date: Re: linux-next: manual merge of the powerpc tree with the dma-mapping tree
Next by Date: RE: linux-next: build failure after merge of the rpmsg tree
Previous by thread: linux-next: build failure after merge of the rpmsg tree
Next by thread: RE: linux-next: build failure after merge of the rpmsg tree
Index(es):
- Date
- Thread

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

Powered by Linux