From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Michal Kubiak <michal.kubiak@intel.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vincent MAILHOL <mailhol.vincent@wanadoo.fr>,
Simon Horman <simon.horman@corigine.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] can: tcan4x5x: Introduce tcan4552/4553
Date: Wed, 15 Mar 2023 11:44:31 +0100 [thread overview]
Message-ID: <20230315104431.xv7md4jcmpw4tkdr@blmsp> (raw)
In-Reply-To: <ZBC8cw/yLiv9L9OM@localhost.localdomain>
Hi Michal,
On Tue, Mar 14, 2023 at 07:26:59PM +0100, Michal Kubiak wrote:
> On Tue, Mar 14, 2023 at 04:11:56PM +0100, Markus Schneider-Pargmann wrote:
> > Hi Marc and everyone,
> >
> > This series introduces two new chips tcan-4552 and tcan-4553. The
> > generic driver works in general but needs a few small changes. These are
> > caused by the removal of wake and state pins.
> >
> > I included two patches from the optimization series and will remove them
> > from the optimization series. Hopefully it avoids conflicts and not
> > polute the other series with tcan4552/4553 stuff.
> >
> > Best,
> > Markus
> >
> > optimization series:
> > https://lore.kernel.org/lkml/20221221152537.751564-1-msp@baylibre.com
> >
> > Markus Schneider-Pargmann (5):
> > dt-bindings: can: tcan4x5x: Add tcan4552 and tcan4553 variants
> > can: tcan4x5x: Remove reserved register 0x814 from writable table
> > can: tcan4x5x: Check size of mram configuration
> > can: tcan4x5x: Rename ID registers to match datasheet
> > can: tcan4x5x: Add support for tcan4552/4553
> >
> > .../devicetree/bindings/net/can/tcan4x5x.txt | 11 +-
> > drivers/net/can/m_can/m_can.c | 16 +++
> > drivers/net/can/m_can/m_can.h | 1 +
> > drivers/net/can/m_can/tcan4x5x-core.c | 122 ++++++++++++++----
> > drivers/net/can/m_can/tcan4x5x-regmap.c | 1 -
> > 5 files changed, 121 insertions(+), 30 deletions(-)
> >
>
> The logic and coding style looks OK to me, but CAN-specific stuff should
> be reviewed by someone else.
> Just one nitpick in the last patch.
>
> Thanks,
> Michal
>
> For entire series:
> Reviewed-by: Michal Kubiak <michal.kubiak@intel.com>
Thanks for your review, I fixed the nitpick.
Best,
Markus
prev parent reply other threads:[~2023-03-15 10:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 15:11 [PATCH 0/5] can: tcan4x5x: Introduce tcan4552/4553 Markus Schneider-Pargmann
2023-03-14 15:11 ` [PATCH 1/5] dt-bindings: can: tcan4x5x: Add tcan4552 and tcan4553 variants Markus Schneider-Pargmann
2023-03-14 16:13 ` Simon Horman
2023-03-14 20:01 ` Krzysztof Kozlowski
2023-03-15 10:49 ` Markus Schneider-Pargmann
2023-03-15 11:29 ` Marc Kleine-Budde
2023-03-15 11:25 ` Marc Kleine-Budde
2023-03-15 13:14 ` Krzysztof Kozlowski
2023-03-15 15:58 ` Markus Schneider-Pargmann
2023-03-15 16:03 ` Simon Horman
2023-03-15 16:07 ` Krzysztof Kozlowski
2023-03-14 15:11 ` [PATCH 2/5] can: tcan4x5x: Remove reserved register 0x814 from writable table Markus Schneider-Pargmann
2023-03-14 15:11 ` [PATCH 3/5] can: tcan4x5x: Check size of mram configuration Markus Schneider-Pargmann
2023-03-14 15:12 ` [PATCH 4/5] can: tcan4x5x: Rename ID registers to match datasheet Markus Schneider-Pargmann
2023-03-14 15:12 ` [PATCH 5/5] can: tcan4x5x: Add support for tcan4552/4553 Markus Schneider-Pargmann
2023-03-14 16:22 ` Simon Horman
2023-03-15 10:41 ` Markus Schneider-Pargmann
2023-03-14 18:19 ` Michal Kubiak
2023-03-14 18:26 ` [PATCH 0/5] can: tcan4x5x: Introduce tcan4552/4553 Michal Kubiak
2023-03-15 10:44 ` Markus Schneider-Pargmann [this message]
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=20230315104431.xv7md4jcmpw4tkdr@blmsp \
--to=msp@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=michal.kubiak@intel.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rcsekar@samsung.com \
--cc=robh+dt@kernel.org \
--cc=simon.horman@corigine.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