linux-kernel - Re: [GIT PULL] dmaengine updates for 4.3-rc1'

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] [day] [month] [year] [list]

Date:	Thu, 17 Sep 2015 18:38:30 +0530
From:	Vinod Koul <vinod.koul@...el.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	dma <dmaengine@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] dmaengine updates for 4.3-rc1'

On Fri, Sep 04, 2015 at 11:13:27AM -0700, Linus Torvalds wrote:
> On Wed, Sep 2, 2015 at 11:41 PM, Vinod Koul <vinod.koul@...el.com> wrote:
> >
> > Here is the dmaengine update for 4.3-rc1.
> 
> Ugh. Something horrible happened here.
> 
> > New devices added are:
> > - dma controller in sun[457]i SoCs
> 
> This thing is completely broken and causes a lot of nasty error
> messages on 64-bit:
> 
>   drivers/dma/sun4i-dma.c: In function ‘find_and_use_pchan’:
>   drivers/dma/sun4i-dma.c:241:32: warning: passing argument 1 of
> ‘find_next_zero_bit’ from incompatible pointer type
> [-Wincompatible-pointer-types]
>   ...
> 
> and this needs to be fixed.
> 
> I've removed the COMPILE_TEST option for that config in the meantime,
> because I refuse to have my screen fill up with warnings like this.
> 
> COMPILE_TEST is fine for drivers that are supposed to compile cleanly
> even if they might not work - and encouraging people to _keep_ them
> compiling cleanly and get better compile test coverage.
> 
> But it's not fine for stuff that causes big warnings and might hide
> actual real problems.

Sorry about this noise, I will get this fixed

-- 
~Vinod
--
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/