mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Olof Johansson <olof@lixom.net>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Vinod Koul <vinod.koul@intel.com>,
	dmaengine@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr()
Date: Wed, 27 Nov 2013 18:58:51 -0500	[thread overview]
Message-ID: <20131127235851.GS2879@titan.lakedaemon.net> (raw)
In-Reply-To: <CAOesGMhRYg4L72v8XCCSwSnLhYuZ6+aBTxPGNvVn=n=xpVm71A@mail.gmail.com>

On Wed, Nov 27, 2013 at 11:45:24AM -0800, Olof Johansson wrote:
> 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.

Ack.  Dropped.  Sorry for the confusion and thanks for setting me
straight.

thx,

Jason.

  reply	other threads:[~2013-11-27 23:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 19:39 Jason Cooper
2013-11-25 19:46 ` Jason Cooper
2013-11-27 19:45   ` Olof Johansson
2013-11-27 23:58     ` Jason Cooper [this message]
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=20131127235851.GS2879@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=vinod.koul@intel.com \
    /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

all inboxes | Powered by JetHome®