From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: "Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Simon Horman" <horms+renesas@verge.net.au>,
"Jürg Billeter" <j@bitron.ch>,
"Magnus Damm" <damm+renesas@opensource.se>,
"Phil Edworthy" <phil.edworthy@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: Fri, 12 Dec 2014 21:41:11 +0200 [thread overview]
Message-ID: <2800395.CA9KFGZM72@avalon> (raw)
In-Reply-To: <87r3w79ea0.wl%kuninori.morimoto.gx@renesas.com>
(Resend, as the message doesn't seem to have made it to the mailing lists)
On Thursday 11 December 2014 01:16:31 Kuninori Morimoto wrote:
> > > On Mon, Dec 08, 2014 at 11:20:44PM +0530, Vinod Koul wrote:
> > > > On Mon, Dec 08, 2014 at 07:40:15PM +0200, Laurent Pinchart wrote:
> > > >>>> [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 haven't CC'ed you, I'll make sure to do so next time. The mail
> > > >> should still have reached you through the mailing list though (I
> > > >> assume you're subscribed to dmaengine@vger.kernel.org ;-)).
> > > >
> > > > Yes I am, so should have reached me even though i wasnt cced
> > > > I do see email reaching me from list without me being in CC, but then
> > > > it wont hit my inbox and go to ML folder :)
> > > > So generally its a good practice to CC relvant folks, lots of folks do
> > > > ask that if ML is high volume
> > >
> > > Hey Laurent,
> > >
> > > I see that the oddity in commitlogs with change since artifacts after
> > > SOB, can you please fix that up
> >
> > My bad. I've fixed the problem and pushed the result to the same branch
> >
> > git://linuxtv.org/pinchartl/fbdev.git dma/next
> >
> > The only difference lies in the commit logs.
>
> If my understanding was correct, we need to be based on Vinod's
> topic/slave_caps_device_control_fix
Vinod, could you please comment on that ? To which kernel version do you plan
to push this series ? Do I need to rebase it ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-12 19:40 UTC|newest]
Thread overview: 18+ 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-27 0:07 ` Laurent Pinchart
2014-12-08 11:36 ` Vinod Koul
2014-12-08 16:50 ` Jürg Billeter
2014-12-08 17:19 ` Vinod Koul
2014-12-08 17:40 ` Laurent Pinchart
2014-12-08 17:50 ` Vinod Koul
2014-12-09 6:39 ` Vinod Koul
2014-12-10 16:09 ` Laurent Pinchart
2014-12-11 1:16 ` Kuninori Morimoto
2014-12-12 19:41 ` Laurent Pinchart [this message]
2014-12-15 6:38 ` Vinod Koul
2014-12-15 20:04 ` Laurent Pinchart
2014-12-16 7:04 ` Vinod Koul
2014-12-16 23:57 ` Laurent Pinchart
2014-12-17 12:54 ` Vinod Koul
2014-12-22 15:02 ` Vinod Koul
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=2800395.CA9KFGZM72@avalon \
--to=laurent.pinchart@ideasonboard.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=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=phil.edworthy@renesas.com \
--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;
as well as URLs for NNTP newsgroup(s).