From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752590AbbIQNGU (ORCPT <rfc822;w@1wt.eu>);
	Thu, 17 Sep 2015 09:06:20 -0400
Received: from mga14.intel.com ([192.55.52.115]:36456 "EHLO mga14.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751922AbbIQNGP (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 17 Sep 2015 09:06:15 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.17,547,1437462000"; 
   d="scan'208";a="807259333"
Date: Thu, 17 Sep 2015 18:38:30 +0530
From: Vinod Koul <vinod.koul@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] dmaengine updates for 4.3-rc1'
Message-ID: <20150917130830.GR19522@localhost>
References: <20150903064104.GS13546@localhost>
 <CA+55aFw9B6Q4KiScx-u90MN-LjoJO-FTGCaftum5DMPWdTp93Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+55aFw9B6Q4KiScx-u90MN-LjoJO-FTGCaftum5DMPWdTp93Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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@intel.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