From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM: sun8i: Add DMA controller support
Date: Thu, 6 Nov 2014 14:09:29 +0530 [thread overview]
Message-ID: <20141106083929.GY1870@intel.com> (raw)
In-Reply-To: <CAGb2v66m6Q=YX04Yez7HD=P1G5+G_0ej2tAw9dCJMBb+EHpz1g@mail.gmail.com>
On Thu, Nov 06, 2014 at 03:54:35PM +0800, Chen-Yu Tsai wrote:
> > The patches look fine to me so I tried applying them but they fail to apply,
> > can you please rebase these two and resend
>
> Hi Vinod,
>
> Could you publish an updated slave-dma/next branch? Currently I see it at
> v3.18-rc1. And the series rebases cleanly onto it with no differences.
>
> I'm guessing some of Maxime's cleanup work is the source of conflict.
Its pushed now..
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Dan Williams
<dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
linux-sunxi <linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 0/3] ARM: sun8i: Add DMA controller support
Date: Thu, 6 Nov 2014 14:09:29 +0530 [thread overview]
Message-ID: <20141106083929.GY1870@intel.com> (raw)
In-Reply-To: <CAGb2v66m6Q=YX04Yez7HD=P1G5+G_0ej2tAw9dCJMBb+EHpz1g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Nov 06, 2014 at 03:54:35PM +0800, Chen-Yu Tsai wrote:
> > The patches look fine to me so I tried applying them but they fail to apply,
> > can you please rebase these two and resend
>
> Hi Vinod,
>
> Could you publish an updated slave-dma/next branch? Currently I see it at
> v3.18-rc1. And the series rebases cleanly onto it with no differences.
>
> I'm guessing some of Maxime's cleanup work is the source of conflict.
Its pushed now..
--
~Vinod
next prev parent reply other threads:[~2014-11-06 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 3:24 [PATCH v2 0/3] ARM: sun8i: Add DMA controller support Chen-Yu Tsai
2014-09-18 3:24 ` Chen-Yu Tsai
2014-09-18 3:24 ` [PATCH v2 1/3] dmaengine: sun6i: support parameterized compatible strings Chen-Yu Tsai
2014-09-18 3:24 ` Chen-Yu Tsai
2014-09-18 3:24 ` [PATCH v2 2/3] dmaengine: sun6i: Add support for Allwinner A23 (sun8i) variant Chen-Yu Tsai
2014-09-18 3:24 ` Chen-Yu Tsai
2014-09-20 10:33 ` Maxime Ripard
2014-09-20 10:33 ` Maxime Ripard
2014-09-18 3:24 ` [PATCH v2 3/3] ARM: dts: sun8i: Add DMA controller node Chen-Yu Tsai
2014-09-18 3:24 ` Chen-Yu Tsai
2014-09-20 10:39 ` Maxime Ripard
2014-09-20 10:39 ` Maxime Ripard
2014-09-26 3:06 ` [PATCH v2 0/3] ARM: sun8i: Add DMA controller support Chen-Yu Tsai
2014-09-26 3:06 ` Chen-Yu Tsai
2014-11-06 7:11 ` Vinod Koul
2014-11-06 7:11 ` Vinod Koul
2014-11-06 7:54 ` Chen-Yu Tsai
2014-11-06 7:54 ` Chen-Yu Tsai
2014-11-06 8:39 ` Vinod Koul [this message]
2014-11-06 8:39 ` 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=20141106083929.GY1870@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.