From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr()
Date: Wed, 27 Nov 2013 11:45:24 -0800 [thread overview]
Message-ID: <CAOesGMhRYg4L72v8XCCSwSnLhYuZ6+aBTxPGNvVn=n=xpVm71A@mail.gmail.com> (raw)
In-Reply-To: <20131125194631.GE2879@titan.lakedaemon.net>
On Mon, Nov 25, 2013 at 11:46 AM, Jason Cooper <jason@lakedaemon.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@lakedaemon.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
next prev parent reply other threads:[~2013-11-27 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:39 [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr() Jason Cooper
2013-11-25 19:46 ` Jason Cooper
2013-11-27 19:45 ` Olof Johansson [this message]
2013-11-27 23:58 ` Jason Cooper
2013-11-28 5:57 ` Vinod Koul
2013-12-09 23:50 ` Russell King - ARM Linux
2013-12-10 10:13 ` Vinod Koul
2013-12-10 11:14 ` Russell King - ARM Linux
2013-12-11 9:10 ` Dan Williams
2013-12-13 7:00 ` Dan Williams
2013-12-18 15:40 ` Vinod Koul
2013-12-18 16:55 ` Dan Williams
2013-12-18 16:33 ` Vinod Koul
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='CAOesGMhRYg4L72v8XCCSwSnLhYuZ6+aBTxPGNvVn=n=xpVm71A@mail.gmail.com' \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).