linux-kernel - Re: [PATCH] dmaengine: ste_dma40: Declare memcpy config as static

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]

Message-ID: <CACRpkdYRqY9yRutfwgEaRAUGiwV38fs=EVpSP1As8OB0piERiQ@mail.gmail.com>
Date:	Mon, 24 Jun 2013 13:49:54 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Fabio Baltieri <fabio.baltieri@...aro.org>
Cc:	Vinod Koul <vinod.koul@...el.com>,
	Lee Jones <lee.jones@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Srinidhi Kasagar <srinidhi.kasagar@...ricsson.com>
Subject: Re: [PATCH] dmaengine: ste_dma40: Declare memcpy config as static

On Fri, Jun 21, 2013 at 9:33 AM, Fabio Baltieri
<fabio.baltieri@...aro.org> wrote:
> On Fri, Jun 21, 2013 at 08:40:00AM +0530, Vinod Koul wrote:
>> On Thu, Jun 20, 2013 at 11:17:39AM +0200, Fabio Baltieri wrote:
>> > Fix sparse warnings:
>> >
>> > drivers/dma/ste_dma40.c:81:26: warning: symbol 'dma40_memcpy_conf_phy' was not declared. Should it be static?
>> > drivers/dma/ste_dma40.c:95:26: warning: symbol 'dma40_memcpy_conf_log' was not declared. Should it be static?
>> >
>> > Signed-off-by: Fabio Baltieri <fabio.baltieri@...aro.org>
>> Acked-by: Vinod Koul <vinod.koul@...el.com>
>>
>> I guess this would be dependent on recent ste_dma40 patches so best way is
>> Linus's tree, right?
>
> Yes, but I'm not sure Linus is going to send a third pull request for
> dma40 so maybe I should just resend my last two dma40 patches for
> arm-soc directly.

I've stacked it in my tree, I didn't plan to send another pull
request but I guess I have to, or I'll send it as fixes, so I'm
taking care of this.

Yours,
Linus Walleij
--
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/