From: Vinod Koul <vinod.koul@intel.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jason Cooper <jason@lakedaemon.net>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr()
Date: Tue, 10 Dec 2013 15:43:31 +0530 [thread overview]
Message-ID: <20131210101331.GG29580@intel.com> (raw)
In-Reply-To: <20131209235035.GA11632@n2100.arm.linux.org.uk>
On Mon, Dec 09, 2013 at 11:50:35PM +0000, Russell King - ARM Linux wrote:
> On Thu, Nov 28, 2013 at 11:27:06AM +0530, Vinod Koul wrote:
> > + Dan
> >
> > 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>
> > Acked-by: Vinod Koul <vinod.koul@intel.com>
> >
> > This should go thru Dan's tree
>
> So what's happening with this patch? I don't see it in -rc yet.
Dan has applied this to his next. So this should show us in next rc1
--
~Vinod
next prev parent reply other threads:[~2013-12-10 11:11 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
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 [this message]
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=20131210101331.GG29580@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).