From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Conor Dooley <conor+dt@kernel.org>,
Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
Michal Kubiak <michal.kubiak@intel.com>,
Vivek Yadav <vivek.2311@samsung.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH v2 1/6] dt-bindings: can: tcan4x5x: Add tcan4552 and tcan4553 variants
Date: Wed, 21 Jun 2023 14:20:27 +0200 [thread overview]
Message-ID: <20230621122027.k37n23yn62ygi6cq@blmsp> (raw)
In-Reply-To: <315991a3-c825-5df8-2e68-40f24c524df1@linaro.org>
Hi Krzysztof,
On Wed, Jun 21, 2023 at 12:29:40PM +0200, Krzysztof Kozlowski wrote:
> On 21/06/2023 11:30, Markus Schneider-Pargmann wrote:
> > These two new chips do not have state or wake pins.
> >
> > Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
>
> BTW, why did you ignore the tag?
Thanks for your Acked-by.
I did not add it from v1 because:
- We had a long discussion after you sent your tag
- I changed the binding documentation according to the discussion on v1
as stated in the cover letter:
"- Update the binding documentation to specify tcan4552 and tcan4553 with
the tcan4x5x as fallback"
Thanks,
Markus
next prev parent reply other threads:[~2023-06-21 12:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 9:30 [PATCH v2 0/6] can: tcan4x5x: Introduce tcan4552/4553 Markus Schneider-Pargmann
2023-06-21 9:30 ` [PATCH v2 1/6] dt-bindings: can: tcan4x5x: Add tcan4552 and tcan4553 variants Markus Schneider-Pargmann
2023-06-21 10:26 ` Krzysztof Kozlowski
2023-06-21 10:29 ` Krzysztof Kozlowski
2023-06-21 12:20 ` Markus Schneider-Pargmann [this message]
2023-06-21 9:30 ` [PATCH v2 2/6] can: tcan4x5x: Remove reserved register 0x814 from writable table Markus Schneider-Pargmann
2023-06-21 9:31 ` [PATCH v2 3/6] can: tcan4x5x: Check size of mram configuration Markus Schneider-Pargmann
2023-06-21 9:31 ` [PATCH v2 4/6] can: tcan4x5x: Rename ID registers to match datasheet Markus Schneider-Pargmann
2023-06-21 9:31 ` [PATCH v2 5/6] can: tcan4x5x: Add support for tcan4552/4553 Markus Schneider-Pargmann
2023-06-21 10:28 ` Krzysztof Kozlowski
2023-06-21 12:31 ` Markus Schneider-Pargmann
2023-06-21 13:00 ` Krzysztof Kozlowski
2023-06-22 12:23 ` Markus Schneider-Pargmann
2023-06-22 12:52 ` Krzysztof Kozlowski
2023-06-27 14:23 ` Markus Schneider-Pargmann
2023-07-01 8:34 ` Krzysztof Kozlowski
2023-07-18 7:57 ` Marc Kleine-Budde
2023-06-21 9:31 ` [PATCH v2 6/6] can: tcan4x5x: Add error messages in probe Markus Schneider-Pargmann
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=20230621122027.k37n23yn62ygi6cq@blmsp \
--to=msp@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rcsekar@samsung.com \
--cc=robh+dt@kernel.org \
--cc=simon.horman@corigine.com \
--cc=vivek.2311@samsung.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