All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Peng Ma <peng.ma@nxp.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Wen He <wen.he_1@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Leo Li <leoyang.li@nxp.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64: dts: ls1046a: add qdma device tree nodes
Date: Sun, 16 Dec 2018 15:43:57 +0800	[thread overview]
Message-ID: <20181216074354.GG13243@dragon> (raw)
In-Reply-To: <VI1PR04MB44313466C33A7BAD7167D4EEEDA10@VI1PR04MB4431.eurprd04.prod.outlook.com>

On Fri, Dec 14, 2018 at 10:30:15AM +0000, Peng Ma wrote:
> Hi shawnguo,
> 
> I send this series patch to http://patchwork.ozlabs.org/project/devicetree-bindings/list/
> But I did not find patchs on devicetree patchwork, could I send patchs again.

You do not need to.  I have sent the series for 4.21 inclusion.  I
forgot to reply and let you know.  Sorry.

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Peng Ma <peng.ma@nxp.com>
Cc: "vkoul@kernel.org" <vkoul@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Wen He <wen.he_1@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Leo Li <leoyang.li@nxp.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64: dts: ls1046a: add qdma device tree nodes
Date: Sun, 16 Dec 2018 15:43:57 +0800	[thread overview]
Message-ID: <20181216074354.GG13243@dragon> (raw)
In-Reply-To: <VI1PR04MB44313466C33A7BAD7167D4EEEDA10@VI1PR04MB4431.eurprd04.prod.outlook.com>

On Fri, Dec 14, 2018 at 10:30:15AM +0000, Peng Ma wrote:
> Hi shawnguo,
> 
> I send this series patch to http://patchwork.ozlabs.org/project/devicetree-bindings/list/
> But I did not find patchs on devicetree patchwork, could I send patchs again.

You do not need to.  I have sent the series for 4.21 inclusion.  I
forgot to reply and let you know.  Sorry.

Shawn

  reply	other threads:[~2018-12-16  7:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 11:18 [v12 1/3] arm: dts: ls1021a: add qdma device tree nodes Peng Ma
2018-12-06 11:18 ` Peng Ma
2018-12-06 11:18 ` [PATCH 2/3] arm64: dts: ls1043a: " Peng Ma
2018-12-06 11:18   ` Peng Ma
2018-12-06 11:18 ` [PATCH 3/3] arm64: dts: ls1046a: " Peng Ma
2018-12-06 11:18   ` Peng Ma
2018-12-14 10:30   ` Peng Ma
2018-12-14 10:30     ` Peng Ma
2018-12-16  7:43     ` Shawn Guo [this message]
2018-12-16  7:43       ` Shawn Guo
  -- strict thread matches above, loose matches on Subject: below --
2018-12-16 13:51 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=20181216074354.GG13243@dragon \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peng.ma@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=wen.he_1@nxp.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 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.