All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Koji Matsuoka <koji.matsuoka.xm@renesas.com>
Subject: Re: [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CAN-FD node
Date: Fri, 1 Apr 2022 17:23:50 +0200	[thread overview]
Message-ID: <YkcZBiX75NT/uqH5@ninjato> (raw)
In-Reply-To: <CAMuHMdUc_MUXFPmkEzHaTGG5oyJNS2QROpe-RdgTpfRcOstU6Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 643 bytes --]


> > Fixes: 92c406ed0a7f ("arm64: dts: renesas: r8a77961: Add CAN nodes")
> 
> I don't think it was forgotten, and think this is not really a fix:
> CAN and CAN-FD are two different devices, with different drivers.

I thought Goda-san tested both interfaces back then, but maybe I was
wrong. Yeah, Fixes tag may be dropped probably.

> > +                       compatible = "renesas,r8a77961-canfd",
> 
> Can you please send a patch to augment the DT bindings?

Sure, will do.

> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> i.e. will queue in renesas-devel for v5.19, with the Fixes tag removed.

Thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-04-01 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 22:33 [PATCH 0/2] arm64: dts: renesas: r8a77961: improvements from BSP Wolfram Sang
2022-03-19 22:33 ` [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CAN-FD node Wolfram Sang
2022-04-01 12:26   ` Geert Uytterhoeven
2022-04-01 15:23     ` Wolfram Sang [this message]
2022-03-19 22:33 ` [PATCH 2/2] arm64: dts: renesas: r8a77961: Add i2c aliases Wolfram Sang
2022-03-30 10:12   ` Geert Uytterhoeven
2022-04-01 15:25     ` Wolfram Sang
2022-04-01 15:47       ` Geert Uytterhoeven

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=YkcZBiX75NT/uqH5@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=geert@linux-m68k.org \
    --cc=koji.matsuoka.xm@renesas.com \
    --cc=linux-renesas-soc@vger.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 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.