From: Heiko Stuebner <heiko@sntech.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Caesar Wang <caesar.upstream@gmail.com>,
Caesar Wang <wxt@rock-chips.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-kernel@vger.kernel.org, shawn.lin@rock-chips.com,
dianders@chromium.org, Rob Herring <robh+dt@kernel.org>,
linux-spi@vger.kernel.org, linux-rockchip@lists.infradead.org,
Mark Brown <broonie@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Sonny Rao <sonnyrao@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform
Date: Mon, 08 Feb 2016 23:21:57 +0100 [thread overview]
Message-ID: <2223201.4nEkyUQu1O@phil> (raw)
In-Reply-To: <20160208131419.GA19598@localhost>
Hi Vinod,
Am Montag, 8. Februar 2016, 18:44:19 schrieb Vinod Koul:
> On Mon, Feb 08, 2016 at 10:27:04AM +0100, Heiko Stuebner wrote:
> > Am Montag, 8. Februar 2016, 08:41:34 schrieb Vinod Koul:
> > > On Mon, Feb 01, 2016 at 02:56:54PM +0800, Caesar Wang wrote:
> > > > Hello Vinod,
> > > >
> > > > Is there any chance apply the DMA patches?:-)
> > >
> > > I was waiting for any ACKs on ARM patches before I merge this series.
> >
> > I think the more regular way is for the driver maintainer to take the
> > driver-specific stuff and the devicetree parts going through the
> > specific arm- tree. But if you really want to take the whole series,
> > for patches 4,5,6
> Yes but that causes cross tree dependencies, which looking at this won't
> be a big problem, so I can safely merge dmaengine changes and rest can go
> thru ARM tree.
>
> Typically submitter should say which tree he/she prefers, which was not
> provided..
>
> So, are all okay to merge the entire series thru dmaengine tree or
> independent. I don't mind either
In general I don't mind either solution, but would prefer me taking the 3
"ARM: dts: foo" patches, while the rest would go through your tree.
Main reason is to prevent any possible conflicts with other Rockchip
devicetree additions also going into 4.6 .
Thanks
Heiko
> > - ARM: dts: Add arm, pl330-broken-no-flushp quirk for rk3288 platform
> > - ARM: dts: Add arm, pl330-broken-no-flushp quirk for rk3xxx platform
> > - ARM: dts: add pl330-broken-no-flushp quirk for rk3036 SoCs
> >
> > Acked-by: Heiko Stuebner <heiko@sntech.de>
>
> Thanks
next prev parent reply other threads:[~2016-02-08 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 11:06 [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Caesar Wang
[not found] ` <1453460812-8498-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-01-22 11:06 ` [PATCH v7 9/9] spi: rockchip: modify DMA max burst to 1 Caesar Wang
2016-02-09 3:34 ` Vinod Koul
2016-02-01 6:56 ` [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Caesar Wang
[not found] ` <56AF01B6.6030204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-08 3:11 ` Vinod Koul
2016-02-08 9:27 ` Heiko Stuebner
2016-02-08 13:14 ` Vinod Koul
2016-02-08 14:02 ` Mark Brown
2016-02-08 22:21 ` Heiko Stuebner [this message]
2016-02-09 3:21 ` 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=2223201.4nEkyUQu1O@phil \
--to=heiko@sntech.de \
--cc=broonie@kernel.org \
--cc=caesar.upstream@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=sonnyrao@chromium.org \
--cc=vinod.koul@intel.com \
--cc=wxt@rock-chips.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).