[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOesGMhRYg4L72v8XCCSwSnLhYuZ6+aBTxPGNvVn=n=xpVm71A@mail.gmail.com>
Date: Wed, 27 Nov 2013 11:45:24 -0800
From: Olof Johansson <olof@...om.net>
To: Jason Cooper <jason@...edaemon.net>
Cc: Dan Williams <dan.j.williams@...el.com>,
Vinod Koul <vinod.koul@...el.com>, dmaengine@...r.kernel.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr()
On Mon, Nov 25, 2013 at 11:46 AM, Jason Cooper <jason@...edaemon.net> wrote:
> On Mon, Nov 25, 2013 at 07:39:25PM +0000, Jason Cooper wrote:
>> The following commit:
>>
>> 54f8d501e842 dmaengine: remove DMA unmap from drivers
>>
>> removed the last caller to mv_desc_get_dest_addr(), creating the
>> warning:
>>
>> drivers/dma/mv_xor.c:57:12: warning: 'mv_desc_get_dest_addr' defined
>> but not used [-Wunused-function]
>>
>> Remove it.
>>
>> Signed-off-by: Jason Cooper <jason@...edaemon.net>
>> ---
>> drivers/dma/mv_xor.c | 6 ------
>> 1 file changed, 6 deletions(-)
>
> Gah! I sent too fast. I meant to mention that I have this in my
> mvebu/fixes branch, which gets merged into -next each night. (The
> warning was bugging me :) )
>
> Just let me know when you take it and I'll drop it from my branches.
Hmm. Please don't add patches for other subsystems into your -next
tree, since then there is no indication for those of us who follow
-next that the patch is not yet merged by the appropriate maintainer.
-Olof
--
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/
Powered by blists - more mailing lists