All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: "Jürg Billeter" <j@bitron.ch>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Simon Horman <horms+renesas@verge.net.au>,
	Magnus Damm <damm+renesas@opensource.se>,
	Phil Edworthy <phil.edworthy@renesas.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
	dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: rcar-dmac: Handle hardware descriptor allocation failure
Date: Mon, 08 Dec 2014 17:31:24 +0000	[thread overview]
Message-ID: <20141208171923.GS16827@intel.com> (raw)
In-Reply-To: <1418057426.5069.6.camel@bitron.ch>

On Mon, Dec 08, 2014 at 05:50:26PM +0100, Jürg Billeter wrote:
> Hi Vinod,
> 
> On Mon, 2014-12-08 at 17:06 +0530, Vinod Koul wrote:
> > Can you please rebase this on my next, this fails to apply for me
> 
> This is a patch for Laurent's new rcar-dmac driver, which doesn't appear
> to be in your next yet. Laurent has already merged my patch into his
> dma/next branch and included it in his pull request from November 27.
> 
> [GIT PULL FOR v3.19] R-Car DMA engine driver
> http://www.spinics.net/lists/linux-sh/msg37764.html
And I dont seem to have this request in my Inbox :(
Yes I do see it in archieves, so not sure how this is not present, not sure
if the servers mangeled it!!

I will pull this tomorrow...

> Please let me know if there is still a rebase required from my side.
Nope

-- 
~Vinod


WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: "Jürg Billeter" <j@bitron.ch>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Simon Horman <horms+renesas@verge.net.au>,
	Magnus Damm <damm+renesas@opensource.se>,
	Phil Edworthy <phil.edworthy@renesas.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
	dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: rcar-dmac: Handle hardware descriptor allocation failure
Date: Mon, 8 Dec 2014 22:49:24 +0530	[thread overview]
Message-ID: <20141208171923.GS16827@intel.com> (raw)
In-Reply-To: <1418057426.5069.6.camel@bitron.ch>

On Mon, Dec 08, 2014 at 05:50:26PM +0100, Jürg Billeter wrote:
> Hi Vinod,
> 
> On Mon, 2014-12-08 at 17:06 +0530, Vinod Koul wrote:
> > Can you please rebase this on my next, this fails to apply for me
> 
> This is a patch for Laurent's new rcar-dmac driver, which doesn't appear
> to be in your next yet. Laurent has already merged my patch into his
> dma/next branch and included it in his pull request from November 27.
> 
> [GIT PULL FOR v3.19] R-Car DMA engine driver
> http://www.spinics.net/lists/linux-sh/msg37764.html
And I dont seem to have this request in my Inbox :(
Yes I do see it in archieves, so not sure how this is not present, not sure
if the servers mangeled it!!

I will pull this tomorrow...

> Please let me know if there is still a rebase required from my side.
Nope

-- 
~Vinod


  reply	other threads:[~2014-12-08 17:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 14:10 [PATCH] dmaengine: rcar-dmac: Handle hardware descriptor allocation failure Jürg Billeter
2014-11-25 14:10 ` Jürg Billeter
2014-11-27  0:07 ` Laurent Pinchart
2014-11-27  0:07   ` Laurent Pinchart
2014-12-08 11:36 ` Vinod Koul
2014-12-08 11:48   ` Vinod Koul
2014-12-08 16:50   ` Jürg Billeter
2014-12-08 16:50     ` Jürg Billeter
2014-12-08 17:19     ` Vinod Koul [this message]
2014-12-08 17:31       ` Vinod Koul
2014-12-08 17:40       ` Laurent Pinchart
2014-12-08 17:40         ` Laurent Pinchart
2014-12-08 17:50         ` Vinod Koul
2014-12-08 17:50           ` Vinod Koul
2014-12-09  6:39           ` Vinod Koul
2014-12-09  6:51             ` Vinod Koul
2014-12-10 16:09             ` Laurent Pinchart
2014-12-10 16:09               ` Laurent Pinchart
2014-12-11  1:16               ` Kuninori Morimoto
2014-12-12 19:41                 ` Laurent Pinchart
2014-12-12 19:41                   ` Laurent Pinchart
2014-12-15  6:38                   ` Vinod Koul
2014-12-15  6:50                     ` Vinod Koul
2014-12-15 20:04                     ` Laurent Pinchart
2014-12-15 20:04                       ` Laurent Pinchart
2014-12-16  7:04                       ` Vinod Koul
2014-12-16  7:16                         ` Vinod Koul
2014-12-16 23:57                         ` Laurent Pinchart
2014-12-16 23:57                           ` Laurent Pinchart
2014-12-17 12:54                           ` Vinod Koul
2014-12-17 12:54                             ` Vinod Koul
2014-12-22 15:02                             ` Vinod Koul
2014-12-22 15:14                               ` Vinod Koul
2014-12-23  9:14                               ` Laurent Pinchart
2014-12-23  9:14                                 ` Laurent Pinchart

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=20141208171923.GS16827@intel.com \
    --to=vinod.koul@intel.com \
    --cc=damm+renesas@opensource.se \
    --cc=dmaengine@vger.kernel.org \
    --cc=horms+renesas@verge.net.au \
    --cc=j@bitron.ch \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=phil.edworthy@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.