All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Michael Trimarchi <michael@amarulasolutions.com>,
	linux-amarula <linux-amarula@amarulasolutions.com>,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	Suniel Mahesh <sunil@amarulasolutions.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH v3 5/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core C.TOUCH 2.0
Date: Thu, 3 Sep 2020 10:25:50 -0600	[thread overview]
Message-ID: <20200903162550.GA2896127@bogus> (raw)
In-Reply-To: <20200831082917.17117-6-jagan@amarulasolutions.com>

On Mon, 31 Aug 2020 13:59:15 +0530, Jagan Teki wrote:
> PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam.
> 
> C.TOUCH 2.0 is a general purpose carrier board with capacitive
> touch interface support.
> 
> PX30.Core needs to mount on top of this Carrier board for creating
> complete PX30.Core C.TOUCH 2.0 board.
> 
> Add bindings for it.
> 
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Changes for v3:
> - none
> Changes for v2:
> - new patch
> 
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 


Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.

If a tag was not added on purpose, please state why and what changed.


WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Suniel Mahesh <sunil@amarulasolutions.com>,
	Michael Trimarchi <michael@amarulasolutions.com>,
	linux-amarula <linux-amarula@amarulasolutions.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 5/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core C.TOUCH 2.0
Date: Thu, 3 Sep 2020 10:25:50 -0600	[thread overview]
Message-ID: <20200903162550.GA2896127@bogus> (raw)
In-Reply-To: <20200831082917.17117-6-jagan@amarulasolutions.com>

On Mon, 31 Aug 2020 13:59:15 +0530, Jagan Teki wrote:
> PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam.
> 
> C.TOUCH 2.0 is a general purpose carrier board with capacitive
> touch interface support.
> 
> PX30.Core needs to mount on top of this Carrier board for creating
> complete PX30.Core C.TOUCH 2.0 board.
> 
> Add bindings for it.
> 
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Changes for v3:
> - none
> Changes for v2:
> - new patch
> 
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 


Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.

If a tag was not added on purpose, please state why and what changed.


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Suniel Mahesh <sunil@amarulasolutions.com>,
	Michael Trimarchi <michael@amarulasolutions.com>,
	linux-amarula <linux-amarula@amarulasolutions.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 5/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core C.TOUCH 2.0
Date: Thu, 3 Sep 2020 10:25:50 -0600	[thread overview]
Message-ID: <20200903162550.GA2896127@bogus> (raw)
In-Reply-To: <20200831082917.17117-6-jagan@amarulasolutions.com>

On Mon, 31 Aug 2020 13:59:15 +0530, Jagan Teki wrote:
> PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam.
> 
> C.TOUCH 2.0 is a general purpose carrier board with capacitive
> touch interface support.
> 
> PX30.Core needs to mount on top of this Carrier board for creating
> complete PX30.Core C.TOUCH 2.0 board.
> 
> Add bindings for it.
> 
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Changes for v3:
> - none
> Changes for v2:
> - new patch
> 
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 


Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.

If a tag was not added on purpose, please state why and what changed.


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

  reply	other threads:[~2020-09-03 16:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  8:29 [PATCH v3 0/7] arm64: dts: rockchip: Add Engicam PX30.Core Jagan Teki
2020-08-31  8:29 ` Jagan Teki
2020-08-31  8:29 ` Jagan Teki
2020-08-31  8:29 ` [PATCH v3 1/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29 ` [PATCH v3 2/7] arm64: dts: rockchip: px30: Add Engicam " Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29 ` [PATCH v3 3/7] arm64: dts: rockchip: Add Engicam PX30.Core SOM Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29 ` [PATCH v3 4/7] arm64: dts: rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29 ` [PATCH v3 5/7] dt-bindings: arm: rockchip: Add Engicam PX30.Core C.TOUCH 2.0 Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-09-03 16:25   ` Rob Herring [this message]
2020-09-03 16:25     ` Rob Herring
2020-09-03 16:25     ` Rob Herring
2020-09-03 16:47     ` Jagan Teki
2020-09-03 16:47       ` Jagan Teki
2020-09-03 16:47       ` Jagan Teki
2020-09-04 14:50       ` Rob Herring
2020-09-04 14:50         ` Rob Herring
2020-09-04 14:50         ` Rob Herring
2020-08-31  8:29 ` [PATCH v3 6/7] arm64: dts: rockchip: px30: Add Engicam " Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31 10:08   ` Johan Jonker
2020-08-31 10:08     ` Johan Jonker
2020-08-31 10:08     ` Johan Jonker
2020-09-01 10:25     ` Jagan Teki
2020-09-01 10:25       ` Jagan Teki
2020-09-01 10:25       ` Jagan Teki
2020-08-31  8:29 ` [PATCH v3 7/7] arm64: dts: rockchip: Add Engicam PX30.Core " Jagan Teki
2020-08-31  8:29   ` Jagan Teki
2020-08-31  8:29   ` Jagan Teki

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=20200903162550.GA2896127@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=michael@amarulasolutions.com \
    --cc=robh+dt@kernel.org \
    --cc=sunil@amarulasolutions.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.