From: Marek Vasut <marek.vasut@gmail.com>
To: Simon Horman <horms@verge.net.au>
Cc: devicetree@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: can: rcar_canfd: document r8a77990 support
Date: Sat, 16 Feb 2019 15:00:17 +0100 [thread overview]
Message-ID: <168f18bc-d104-bc1d-980c-93a10c82c775@gmail.com> (raw)
In-Reply-To: <20181121102017.hza4czc3cnqtfyxn@verge.net.au>
On 11/21/18 11:20 AM, Simon Horman wrote:
> On Sun, Nov 18, 2018 at 06:32:01PM +0100, Marek Vasut wrote:
>> Document the support for rcar_canfd on R8A77990 SoC devices.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>> Cc: Eugeniu Rosca <erosca@de.adit-jv.com>
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: Simon Horman <horms+renesas@verge.net.au>
>> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
>> Cc: linux-renesas-soc@vger.kernel.org
>> To: devicetree@vger.kernel.org
>
> Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
This patchset seems to be missing upstream.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-02-16 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 17:32 [PATCH 1/2] dt-bindings: can: rcar_canfd: document r8a77965 support Marek Vasut
2018-11-18 17:32 ` [PATCH 2/2] dt-bindings: can: rcar_canfd: document r8a77990 support Marek Vasut
2018-11-21 10:20 ` Simon Horman
2019-02-16 14:00 ` Marek Vasut [this message]
2018-11-18 23:18 ` [PATCH 1/2] dt-bindings: can: rcar_canfd: document r8a77965 support Wolfram Sang
2018-11-18 23:21 ` Marek Vasut
2018-11-19 8:43 ` Geert Uytterhoeven
2018-11-19 9:40 ` Geert Uytterhoeven
2018-11-19 10:41 ` Simon Horman
2018-11-19 10:53 ` Wolfram Sang
2018-11-21 10:20 ` Simon Horman
2018-12-04 22:56 ` Rob Herring
2018-12-04 23:44 ` Marek Vasut
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=168f18bc-d104-bc1d-980c-93a10c82c775@gmail.com \
--to=marek.vasut@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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 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).