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'
Date: Thu, 17 Sep 2015 18:38:30 +0530 [thread overview]
Message-ID: <20150917130830.GR19522@localhost> (raw)
In-Reply-To: <CA+55aFw9B6Q4KiScx-u90MN-LjoJO-FTGCaftum5DMPWdTp93Q@mail.gmail.com>
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
prev parent reply other threads:[~2015-09-17 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 6:41 [GIT PULL] dmaengine updates for 4.3-rc1 Vinod Koul
2015-09-04 18:13 ` Linus Torvalds
2015-09-17 13:08 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150917130830.GR19522@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.