From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] dt-bindings: ls1012a: Add FRWY-LS1012A device tree binding
Date: Wed, 31 Oct 2018 14:48:12 +0800 [thread overview]
Message-ID: <20181031064809.GF10386@tiger> (raw)
In-Reply-To: <20181026084554.32290-1-pramod.kumar_1@nxp.com>
On Fri, Oct 26, 2018 at 08:45:26AM +0000, Pramod Kumar wrote:
> LS1012A-FRWY is an ls1012a based SoC board
> Add device tree binding for LS1012A-FRWY board
>
> Signed-off-by: Pramod Kumar <pramod.kumar_1@nxp.com>
It should really be sent together with "arm64: dts: ls1012a: Add
FRWY-LS1012A board support" as a patch series.
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Pramod Kumar <pramod.kumar_1@nxp.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Leo Li <leoyang.li@nxp.com>
Subject: Re: [PATCH v2] dt-bindings: ls1012a: Add FRWY-LS1012A device tree binding
Date: Wed, 31 Oct 2018 14:48:12 +0800 [thread overview]
Message-ID: <20181031064809.GF10386@tiger> (raw)
In-Reply-To: <20181026084554.32290-1-pramod.kumar_1@nxp.com>
On Fri, Oct 26, 2018 at 08:45:26AM +0000, Pramod Kumar wrote:
> LS1012A-FRWY is an ls1012a based SoC board
> Add device tree binding for LS1012A-FRWY board
>
> Signed-off-by: Pramod Kumar <pramod.kumar_1@nxp.com>
It should really be sent together with "arm64: dts: ls1012a: Add
FRWY-LS1012A board support" as a patch series.
Applied, thanks.
next prev parent reply other threads:[~2018-10-31 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 8:45 [PATCH v2] dt-bindings: ls1012a: Add FRWY-LS1012A device tree binding Pramod Kumar
2018-10-26 8:45 ` Pramod Kumar
2018-10-30 21:47 ` Rob Herring
2018-10-30 21:47 ` Rob Herring
2018-10-31 6:48 ` Shawn Guo [this message]
2018-10-31 6:48 ` Shawn Guo
2018-12-08 2:22 ` Shawn Guo
2018-12-08 2:22 ` Shawn Guo
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=20181031064809.GF10386@tiger \
--to=shawnguo@kernel.org \
--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.