Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp13730964pxu; Mon, 4 Jan 2021 02:55:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJxzF5Vj+RCu7AeAedoiiRSg1PqRcFCvzCqdK+xkYDZHz0MzoJrfl0/IIjj0IP/f6g820SGO X-Received: by 2002:a17:906:2898:: with SMTP id o24mr65337699ejd.215.1609757732460; Mon, 04 Jan 2021 02:55:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609757732; cv=none; d=google.com; s=arc-20160816; b=xZlDaqluxKCwPAyEgpKXCEFdr+W1gLZnFfNQM8sNvOleM0EkpxYoz3l1mHURTSyNpZ OuPGaT+ucUbdkPsd8J6ktkSz2NzT676kH+N25QjXFZP4y/SJ1GnYC4gRtvexb/MdVaq3 PF2RGkCKIpmgrqOIagozP+IZsOX9sfsUABp6CWWY1t/E+9Q7+RRR1tPJWHWF0rj9jIXT jdTg5NX1IPDunO2xJEYmSgDhfmDMKm2pYP6jNX/SscLrKudjWTjDyxNPLO4QGuigQuDH 4qYD8ZFO6tUD0awU7wgcWLh7DWkHNllvGNTwZm800Y3C9KwyqbK41XoCv6DEEdX6mLF0 QWVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=Q0c1Y3LPa+ARd4G//BxkyHoz21dY5cJnRVsgk53Tbn0=; b=P+n/+zcTbapKik2BXivdScMT9Y8JjWTKTom/yaUFVSfmJR4/QGHRcsfBLCcWGJfqxV /nFuuv2hl9oV+dvZrLccWyNmAIams+ODSOgqAzVcrn+bXQsosluXmVLDgkMsS4J45D7W g1FBM7nejMs+J0xc3unrx7Qt0Ngb+CFXzehn//8HxV4kPL2ELvp87l7TGX+aTtTSiiSv 9QRCFJI9Ko/pYSJkK+8WLmBwn0MtaWqC+eLXOH1KFhui23g/fA+z5qJywBWcUtHLmrs9 iynvmpVCiCvFt9RMkTbWKi1JPFPsOogSk3UZa9kFsU3m0uOaH4zy93uuhl7QnV8L+DW9 Fb8A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k17si28037927ejc.181.2021.01.04.02.55.08; Mon, 04 Jan 2021 02:55:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726711AbhADKwX (ORCPT + 99 others); Mon, 4 Jan 2021 05:52:23 -0500 Received: from mail-oo1-f45.google.com ([209.85.161.45]:34674 "EHLO mail-oo1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726129AbhADKwX (ORCPT ); Mon, 4 Jan 2021 05:52:23 -0500 Received: by mail-oo1-f45.google.com with SMTP id x23so6181519oop.1; Mon, 04 Jan 2021 02:52:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q0c1Y3LPa+ARd4G//BxkyHoz21dY5cJnRVsgk53Tbn0=; b=W2qolnfRpSNOO2OPET4j501GZ6Fbc3ix9/s35u7f2ncBvczG8Kuep0IsneSeOvRgbM LHJe1xNLSIF+3rPwk37OCQKnanEsCckhOJHRdFhCPgrOLruGpfZRBK9+GvxM/hkdmCfz DkiIM1qGywXwkhOxgUzQgNZGJDHyoHsdlLjq4UYUNEcTmQCODczWIus72CpYNdOOO7vu zFMEp0Juq80U/0fdPv7qtEN8yBLuRt0HlcDc6h8u5KiAtctNbqsQ9+3YEE6Ny/v/sSWt uX8TC+ZW0nwJOVOrDkYKw5MT5mDYa7+aLW5O+JZX7cX7RrsisHeZhIzytloZvyaL8pj4 EPfw== X-Gm-Message-State: AOAM530a99uL6vF7UTuXVr4D0qYlWN2ocgbfSUT97D54nKcDX4MJ+C3k aGzFRMG5vMAFmevVG2picUnPZR5K6MT+iXsLQkk= X-Received: by 2002:a4a:ca14:: with SMTP id w20mr48712009ooq.11.1609757502401; Mon, 04 Jan 2021 02:51:42 -0800 (PST) MIME-Version: 1.0 References: <20201231155957.31165-1-prabhakar.mahadev-lad.rj@bp.renesas.com> In-Reply-To: <20201231155957.31165-1-prabhakar.mahadev-lad.rj@bp.renesas.com> From: Geert Uytterhoeven Date: Mon, 4 Jan 2021 11:51:31 +0100 Message-ID: Subject: Re: [PATCH] can: rcar: Update help description for CAN_RCAR_CANFD config To: Lad Prabhakar Cc: Wolfgang Grandegger , Marc Kleine-Budde , "David S. Miller" , Jakub Kicinski , Masahiro Yamada , linux-can@vger.kernel.org, netdev , Linux Kernel Mailing List , Linux-Renesas , Prabhakar Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Prabhakar, On Thu, Dec 31, 2020 at 5:00 PM Lad Prabhakar wrote: > The rcar_canfd driver supports R-Car Gen3 and RZ/G2 SoC's, update the > description to reflect this. > > Signed-off-by: Lad Prabhakar Reviewed-by: Geert Uytterhoeven > --- a/drivers/net/can/rcar/Kconfig > +++ b/drivers/net/can/rcar/Kconfig > @@ -10,13 +10,13 @@ config CAN_RCAR > be called rcar_can. > > config CAN_RCAR_CANFD > - tristate "Renesas R-Car CAN FD controller" > + tristate "Renesas R-Car Gen3 and RZ/G2 CAN FD controller" > depends on ARCH_RENESAS || ARM Not introduced by this patch, but the "|| ARM" looks strange to me. Is this meant for compile-testing? Doesn't the driver compile on all platforms (it does on m68k), so "|| COMPILE_TEST" is not appropriate? Is the CAN FD controller present on some Renesas arm32 SoCs (but not yet supported by this driver)? > help > Say Y here if you want to use CAN FD controller found on > - Renesas R-Car SoCs. The driver puts the controller in CAN FD only > - mode, which can interoperate with CAN2.0 nodes but does not support > - dedicated CAN 2.0 mode. > + Renesas R-Car Gen3 and RZ/G2 SoCs. The driver puts the > + controller in CAN FD only mode, which can interoperate with > + CAN2.0 nodes but does not support dedicated CAN 2.0 mode. > > To compile this driver as a module, choose M here: the module will > be called rcar_canfd. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds