From: Shawn Guo <shawnguo@kernel.org>
To: Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>
Cc: corbet@lwn.net, robh+dt@kernel.org, mark.rutland@arm.com,
gregkh@linuxfoundation.org, catalin.marinas@arm.com,
will@kernel.org, leoyang.li@nxp.com, jslaby@suse.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 0/5] Add initial support for S32V234-EVB
Date: Sat, 26 Oct 2019 21:44:04 +0800 [thread overview]
Message-ID: <20191026134403.GQ14401@dragon> (raw)
In-Reply-To: <1571230107-8493-1-git-send-email-stefan-gabriel.mirea@nxp.com>
On Wed, Oct 16, 2019 at 03:48:22PM +0300, Stefan-Gabriel Mirea wrote:
> Eddy Petrișor (1):
> dt-bindings: arm: fsl: Add the S32V234-EVB board
>
> Mihaela Martinas (2):
> arm64: Introduce config for S32
> arm64: defconfig: Enable configs for S32V234
...
> Stoica Cosmin-Stefan (1):
> arm64: dts: fsl: Add device tree for S32V234-EVB
Applied these 4, thanks.
prev parent reply other threads:[~2019-10-26 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 12:48 [PATCH v7 0/5] Add initial support for S32V234-EVB Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 1/5] dt-bindings: arm: fsl: Add the S32V234-EVB board Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 2/5] arm64: Introduce config for S32 Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 3/5] serial: fsl_linflexuart: Be consistent with the name Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 4/5] arm64: dts: fsl: Add device tree for S32V234-EVB Stefan-Gabriel Mirea
2019-10-26 13:42 ` Shawn Guo
2019-10-16 12:48 ` [PATCH v7 5/5] arm64: defconfig: Enable configs for S32V234 Stefan-Gabriel Mirea
2019-10-16 13:17 ` [PATCH v7 0/5] Add initial support for S32V234-EVB Greg KH
2019-10-16 16:54 ` Stefan-gabriel Mirea
2019-10-26 13:26 ` Shawn Guo
2019-10-26 15:12 ` Stefan-gabriel Mirea
2019-10-26 13:44 ` Shawn Guo [this message]
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=20191026134403.GQ14401@dragon \
--to=shawnguo@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan-gabriel.mirea@nxp.com \
--cc=will@kernel.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 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).