[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250219-xanthic-elephant-of-jest-9b5720-mkl@pengutronix.de>
Date: Wed, 19 Feb 2025 12:00:17 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Dimitri Fedrau <dima.fedrau@...il.com>
Cc: Dimitri Fedrau via B4 Relay <devnull+dimitri.fedrau.liebherr.com@...nel.org>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-can@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Dimitri Fedrau <dimitri.fedrau@...bherr.com>
Subject: Re: [PATCH 2/2] can: flexcan: add transceiver capabilities
On 19.02.2025 11:39:55, Dimitri Fedrau wrote:
> > > diff --git a/drivers/net/can/flexcan/flexcan.h b/drivers/net/can/flexcan/flexcan.h
> > > index 4933d8c7439e62b5d6fcc445d88c2b5ccbfa13bb..56be40875eee24aee9297c4bc7c2fc4380e682ff 100644
> > > --- a/drivers/net/can/flexcan/flexcan.h
> > > +++ b/drivers/net/can/flexcan/flexcan.h
> > > @@ -103,6 +103,7 @@ struct flexcan_priv {
> > > struct clk *clk_per;
> > > struct flexcan_devtype_data devtype_data;
> > > struct regulator *reg_xceiver;
> > > + struct phy *xceiver;
> >
> > All other drivers name this variable "transceiver", does it make sense
> > to use this name here, too?
> >
> I have no preference on this, but my intention was to name it xceiver
> according to reg_xceiver, so people familiar with the code would know
> what it is about. I can change it to transceiver, what do you think ?
Please use transceiver.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists