From: "Chandrasekar R" <rcsekar@samsung.com>
To: "'Marc Kleine-Budde'" <mkl@pengutronix.de>, <linux-can@vger.kernel.org>
Cc: "'Rob Herring'" <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>,
"'Benjamin Gaignard'" <benjamin.gaignard@st.com>
Subject: RE: [PATCH net-next] dt-binding: can: m_can: fix indention of table in bosch,mram-cfg description
Date: Thu, 17 Feb 2022 21:28:35 +0530 [thread overview]
Message-ID: <006f01d82417$39d94e20$ad8bea60$@samsung.com> (raw)
In-Reply-To: <20220217101111.2291151-1-mkl@pengutronix.de>
> -----Original Message-----
> From: Marc Kleine-Budde <mkl@pengutronix.de>
> Sent: 17 February 2022 15:41
> To: linux-can@vger.kernel.org
> Cc: Rob Herring <robh+dt@kernel.org>; devicetree@vger.kernel.org; Marc
> Kleine-Budde <mkl@pengutronix.de>; Sriram Dash
> <sriram.dash@samsung.com>; Benjamin Gaignard
> <benjamin.gaignard@st.com>
> Subject: [PATCH net-next] dt-binding: can: m_can: fix indention of table
in
> bosch,mram-cfg description
>
> This patch fixes the indention of the table in the description of the
> bosch,mram-cfg property.
>
> Cc: Sriram Dash <sriram.dash@samsung.com>
This id does not exists anymore.
> Cc: Benjamin Gaignard <benjamin.gaignard@st.com>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
Changes looks fine,
Reviewed-by: Chandrasekar Ramakrishnan <rcsekar@samsung.com>
> Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> index 61f9e512c346..3bc1ed39a0a5 100644
> --- a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> +++ b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> @@ -69,8 +69,8 @@ properties:
> M_CAN includes the following elements according to user manual:
> 11-bit Filter 0-128 elements / 0-128 words
> 29-bit Filter 0-64 elements / 0-128 words
> - Rx FIFO 0 0-64 elements / 0-1152 words
> - Rx FIFO 1 0-64 elements / 0-1152 words
> + Rx FIFO 0 0-64 elements / 0-1152 words
> + Rx FIFO 1 0-64 elements / 0-1152 words
> Rx Buffers 0-64 elements / 0-1152 words
> Tx Event FIFO 0-32 elements / 0-64 words
> Tx Buffers 0-32 elements / 0-576 words
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2022-02-17 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220217130613epcas5p148a75f63b455ad14decf075f1842114b@epcas5p1.samsung.com>
2022-02-17 10:11 ` [PATCH net-next] dt-binding: can: m_can: fix indention of table in bosch,mram-cfg description Marc Kleine-Budde
2022-02-17 10:25 ` Marc Kleine-Budde
[not found] ` <CGME20220217102535epcas5p28ce4527b5f60d9cb347c3e408d930d6a@epcms5p8>
[not found] ` <1851788297.2379.1645096655629@mail-kr5-0>
2022-02-17 11:36 ` Marc Kleine-Budde
2022-02-17 11:40 ` Marc Kleine-Budde
2022-02-17 15:58 ` Chandrasekar R [this message]
2022-02-17 20:16 ` Marc Kleine-Budde
2022-02-25 16:33 ` Rob Herring
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='006f01d82417$39d94e20$ad8bea60$@samsung.com' \
--to=rcsekar@samsung.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).