From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfgang Grandegger <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Prabhakar <prabhakar.csengg@gmail.com>
Subject: Re: [PATCH] can: rcar: Update help description for CAN_RCAR config
Date: Mon, 4 Jan 2021 09:46:22 +0100 [thread overview]
Message-ID: <f565b2f7-16b1-eb64-c1a8-8c8c9dce50dc@pengutronix.de> (raw)
In-Reply-To: <TYBPR01MB530929B7507AFED04F4BADAF86D50@TYBPR01MB5309.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 670 bytes --]
On 1/1/21 6:06 PM, Biju Das wrote:
>> The rcar_can driver supports R-Car Gen{1,2,3} and RZ/G{1,2} SoC's, update
>> the description to reflect this.
>
> Not sure we need to make it generic like dropping {1,2,3}/{1,2} and instead
> use R-Car and RZ/G SoC's??
Sounds good. Better make the description more generic instead of updating it
each time a new SoC comes along.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-04 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 15:59 [PATCH] can: rcar: Update help description for CAN_RCAR_CANFD config Lad Prabhakar
2020-12-31 15:59 ` [PATCH] can: rcar: Update help description for CAN_RCAR config Lad Prabhakar
2021-01-01 17:06 ` Biju Das
2021-01-04 8:46 ` Marc Kleine-Budde [this message]
2021-01-04 10:51 ` [PATCH] can: rcar: Update help description for CAN_RCAR_CANFD config Geert Uytterhoeven
2021-01-04 13:37 ` Lad, Prabhakar
2021-01-04 14:01 ` 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=f565b2f7-16b1-eb64-c1a8-8c8c9dce50dc@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=wg@grandegger.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).