[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230919075135.7xim2yjwt5jna4sy@blmsp>
Date: Tue, 19 Sep 2023 09:51:35 +0200
From: Markus Schneider-Pargmann <msp@...libre.com>
To: Sean Anderson <sean.anderson@...o.com>
Cc: Wolfgang Grandegger <wg@...ndegger.com>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Conor Dooley <conor+dt@...nel.org>,
Chandrasekar Ramakrishnan <rcsekar@...sung.com>,
Michal Kubiak <michal.kubiak@...el.com>,
Vivek Yadav <vivek.2311@...sung.com>,
linux-can@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Simon Horman <simon.horman@...igine.com>
Subject: Re: [PATCH v3 5/6] can: tcan4x5x: Add support for tcan4552/4553
Hi Sean,
On Fri, Sep 15, 2023 at 11:36:49AM -0400, Sean Anderson wrote:
> On 7/21/23 09:50, Markus Schneider-Pargmann wrote:
> > +static const struct tcan4x5x_version_info tcan4x5x_versions[] = {
> > + [TCAN4552] = {
> > + .name = "4552",
> > + .id2_register = 0x32353534,
> > + },
> > + [TCAN4553] = {
> > + .name = "4553",
> > + .id2_register = 0x32353534,
>
> Should this be 0x33353534?
Thank you for noticing! Yes. Probably slipped through in the last
refactoring. I will send a fix.
Best,
Markus
Powered by blists - more mailing lists