From: Vinod Koul <vinod.koul@intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.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: Wed, 17 Dec 2014 12:54:35 +0000 [thread overview]
Message-ID: <20141217125406.GD16827@intel.com> (raw)
In-Reply-To: <5322978.GxSKO5eTNh@avalon>
On Wed, Dec 17, 2014 at 01:57:30AM +0200, Laurent Pinchart wrote:
> Do you mean that every Intel employee needs to resubscribe to all vger mailing
> list once a year ? :-o
Unfortuntely yes... :( I need to set my infradead account up again now for
backup..
>
> > > I suppose I have no choice anyway. Please provide me with a v3.20
> > > development branch on which I can rebase the patch set, I don't want to
> > > rebase it twice.
> >
> > Please use topic/slave_caps_device_control_fix. I am going to rebase this
> > once rc1 is declared (eow i guess). It would plain git rebase, so shouldn't
> > impact you.
>
> Done. I'll rebase it once again when you will have rebased your branch, and
> will then send a pull request. Could you please rebase your branch early after
> the -rc1 release ?
Sure, within a day or so of its release it should be done.
Do note that am out during Christmas and the weekend with no email access,
will be lucky if my phone works, email very unlikely and I think you guys
will be out too.
But if your patches are done, feel free to send them
--
~Vinod
next prev parent reply other threads:[~2014-12-17 12:54 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:48 ` Vinod Koul
2014-12-08 16:50 ` Jürg Billeter
2014-12-08 17:31 ` Vinod Koul
2014-12-08 17:40 ` Laurent Pinchart
2014-12-08 17:50 ` Vinod Koul
2014-12-09 6:51 ` Vinod Koul
2014-12-10 16:09 ` Laurent Pinchart
2014-12-11 1:16 ` Kuninori Morimoto
2014-12-12 19:41 ` Laurent Pinchart
2014-12-15 6:50 ` Vinod Koul
2014-12-15 20:04 ` Laurent Pinchart
2014-12-16 7:16 ` Vinod Koul
2014-12-16 23:57 ` Laurent Pinchart
2014-12-17 12:54 ` Vinod Koul [this message]
2014-12-22 15:14 ` 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=20141217125406.GD16827@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@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 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).