Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933690AbaLKBQk (ORCPT ); Wed, 10 Dec 2014 20:16:40 -0500 Received: from relmlor4.renesas.com ([210.160.252.174]:28125 "EHLO relmlie3.idc.renesas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933505AbaLKBQg (ORCPT ); Wed, 10 Dec 2014 20:16:36 -0500 X-IronPort-AV: E=Sophos;i="5.07,554,1413212400"; d="scan'208";a="176577004" Message-ID: <87r3w79ea0.wl%kuninori.morimoto.gx@renesas.com> From: Kuninori Morimoto To: Laurent Pinchart CC: Vinod Koul , Simon Horman , =?ISO-2022-JP-2?B?ShskKEQrZBsoQnJn?= Billeter , Magnus Damm , Phil Edworthy , , , Subject: Re: [PATCH] dmaengine: rcar-dmac: Handle hardware descriptor allocation failure In-Reply-To: <2735456.CKbC358ZrM@avalon> References: <1416924617-15939-1-git-send-email-j@bitron.ch> <20141208175044.GT16827@intel.com> <20141209063912.GZ16827@intel.com> <2735456.CKbC358ZrM@avalon> User-Agent: Wanderlust/2.14.0 Emacs/23.3 Mule/6.0 MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="US-ASCII" Date: Thu, 11 Dec 2014 01:16:31 +0000 X-Originating-IP: [211.11.155.132] X-ClientProxiedBy: SIXPR06CA0058.apcprd06.prod.outlook.com (25.160.171.176) To HKXPR06MB167.apcprd06.prod.outlook.com (10.242.124.19) X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:HKXPR06MB167; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601003);SRVR:HKXPR06MB167; X-Forefront-PRVS: 0422860ED4 X-Forefront-Antispam-Report: SFV:NSPM;SFS:(10019020)(979002)(6009001)(24454002)(189002)(51704005)(199003)(68736005)(36756003)(92566001)(23726002)(47776003)(106356001)(77096005)(15975445007)(105586002)(64706001)(33646002)(76176999)(31966008)(54356999)(50986999)(46406003)(86362001)(107046002)(77156002)(4396001)(62966003)(50466002)(122386002)(20776003)(81156004)(40100003)(46102003)(53416004)(19580405001)(93886004)(19580395003)(87976001)(83506001)(97736003)(42186005)(99396003)(120916001)(66066001)(101416001)(21056001)(69596002)(110136001)(969003)(989001)(999001)(1009001)(1019001);DIR:OUT;SFP:1102;SCL:1;SRVR:HKXPR06MB167;H:remon.renesas.com;FPR:;SPF:None;MLV:ovrnspm;PTR:InfoNoRecords;MX:1;A:1;LANG:en; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:HKXPR06MB167; X-OriginatorOrg: renesas.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Laurent > > 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 Best regards --- Kuninori Morimoto -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/