linux-kernel - Re: linux-next: build failure after merge of the async

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTilGB0xf7qSDAdFTlaRgcqmf0PexkfczaKCFG06C@mail.gmail.com>
Date:	Mon, 24 May 2010 10:59:22 +0900
From:	Jassi Brar <jassisinghbrar@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Dan Williams <dan.j.williams@...el.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jassi Brar <jassi.brar@...sung.com>
Subject: Re: linux-next: build failure after merge of the async_tx tree

On Mon, May 24, 2010 at 10:24 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:

.....

> Caused by commit 0376653c268fce662831fbd109ce9811b25c16c2 ("DMA: PL330:
> Add dma api driver").  Maybe this depends on a particular architecture?

This driver is for any platform that has the ARM's Primcell DMAC
PL330. So there is no dependency on ARCH_xxxx
Any platform with such a DMAC should select PL330 and this driver
had better be build depending upon PL330 rather than selecting  PL330.

Something like...

config PL330_DMA
       tristate "DMA API Driver for PL330"
       select DMA_ENGINE
-       select PL330
+      depends on PL330
       help
         Select if your platform has one or more PL330 DMACs.
         You need to provide platform specific settings via
         platform_data for a dma-pl330 device.

I am not aware of how such issues are fixed at this stage, please
let me know what is expected of me.

Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/