public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel•org>
To: Peng Ma <peng.ma@nxp•com>
Cc: mark.rutland@arm•com, devicetree@vger•kernel.org,
	Wen He <wen.he_1@nxp•com>,
	linux-kernel@vger•kernel.org, leoyang.li@nxp•com,
	zw@zh-kernel•org, vkoul@kernel•org, robh+dt@kernel•org,
	dmaengine@vger•kernel.org, dan.j.williams@intel•com,
	linuxppc-dev@lists•ozlabs.org,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [v11 4/7] arm: dts: ls1021a: add qdma device tree nodes
Date: Thu, 6 Dec 2018 09:02:38 +0800	[thread overview]
Message-ID: <20181206010237.GP3987@dragon> (raw)
In-Reply-To: <20181030023604.34027-4-peng.ma@nxp.com>

On Tue, Oct 30, 2018 at 10:36:01AM +0800, Peng Ma wrote:
> add the qDMA device tree nodes for LS1021A devices.
> 
> Signed-off-by: Wen He <wen.he_1@nxp•com>
> Signed-off-by: Peng Ma <peng.ma@nxp•com>

Applied, thanks.

  reply	other threads:[~2018-12-06  1:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30  2:35 [v11 1/7] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT Peng Ma
2018-10-30  2:35 ` [v11 2/7] dmaengine: fsldma: Adding macro FSL_DMA_IN/OUT implement for ARM platform Peng Ma
2018-10-30  2:36 ` [v11 3/7] dmaengine: fsl-qdma: Add qDMA controller driver for Layerscape SoCs Peng Ma
2018-10-30  2:36 ` [v11 4/7] arm: dts: ls1021a: add qdma device tree nodes Peng Ma
2018-12-06  1:02   ` Shawn Guo [this message]
2018-10-30  2:36 ` [v11 5/7] arm64: dts: ls1043a: " Peng Ma
2018-12-06  1:04   ` Shawn Guo
2018-10-30  2:36 ` [v11 6/7] arm64: dts: ls1046a: " Peng Ma
2018-12-06  1:05   ` Shawn Guo
2018-12-06 11:04     ` Peng Ma
2018-10-30  2:36 ` [v11 7/7] dt-bindings: fsl-qdma: Add NXP Layerscpae qDMA controller bindings Peng Ma
2018-12-05 17:49 ` [v11 1/7] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT Vinod Koul
2018-12-06 11:24   ` Peng Ma

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=20181206010237.GP3987@dragon \
    --to=shawnguo@kernel$(echo .)org \
    --cc=dan.j.williams@intel$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=dmaengine@vger$(echo .)kernel.org \
    --cc=leoyang.li@nxp$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=peng.ma@nxp$(echo .)com \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=vkoul@kernel$(echo .)org \
    --cc=wen.he_1@nxp$(echo .)com \
    --cc=zw@zh-kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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