From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marek Vasut <marek.vasut@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<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>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: can: rcar_can: document r8a77990 support
Date: Mon, 19 Nov 2018 11:52:57 +0100 [thread overview]
Message-ID: <20181119105256.GA932@kunai> (raw)
In-Reply-To: <CAMuHMdXHK-asgL-9-PTjjYG1gA21qcxaTGy7H13BXVhdrw7u+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
> Marek: I think you misunderstood Wolfram's question.
> He asked about the DT bindings, not about the driver.
Exactly.
> Wolfram: Eugenu's commit 4f145f14f6b98b5a ("dt-bindings: can:
> rcar_can: document r8a77965 support") is in next as of next-20181115 .
> However, it's not part of linux-can-next. Seems to be destined for v4.20 as
> a fix.
Thanks, Geert!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-19 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 17:30 [PATCH] dt-bindings: can: rcar_can: document r8a77990 support Marek Vasut
2018-11-18 23:14 ` Wolfram Sang
2018-11-18 23:22 ` Marek Vasut
2018-11-19 9:38 ` Geert Uytterhoeven
2018-11-19 10:52 ` Wolfram Sang [this message]
2018-11-19 14:19 ` Marek Vasut
2018-11-19 19:32 ` Geert Uytterhoeven
2018-11-19 10:42 ` Simon Horman
2019-02-16 13:58 ` Marek Vasut
2019-08-21 8:06 ` Geert Uytterhoeven
2018-12-04 22:46 ` Rob Herring
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=20181119105256.GA932@kunai \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@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).