Re: [PATCH 00/30] dmaengine: add COMPILE_TEST to drivers

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

 



On Thursday, September 15, 2016 11:03:39 PM CEST Vinod Koul wrote:
> We recently had a conversation about me cribbing that some drivers being
> hard to compile [1]. Arnd suggested [2] to add COMPILE_TEST to these so
> right now. With this I have one ARM config which compiles all drivers.
> 
> I used multi_v7 default config and checked the drivers which are not
> compiling and starting fixing them. So most of them were pretty fine, few
> got warning mostly on bad usage of print specifiers with dma_addr_t and
> size_t being major culprits there and few sparse warnings.
> 
> While compile testing most of the driver compiled fine on others (i have
> used ppc, arm, x86_64, i386, mips) expect the two where we explicitly depends
> on ARM, one is omap and second one is tegra. Jz one had issues but I moved
> header out of arm, so it worked fine.
> They have some API dependency, which we should resolve later..
> 
> Please test...
> 

Very nice series. If you have a git tree with these patches, I
can add the branch to my randconfig testing to see if I get
any build regression on 32-bit ARM.

	Arnd

--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux PCI]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux