From: Simon Horman <simon.horman@corigine.com>
To: Vincent MAILHOL <mailhol.vincent@wanadoo.fr>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, Thomas.Kopp@microchip.com,
Oliver Hartkopp <socketcan@hartkopp.net>,
netdev@vger.kernel.org, marex@denx.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] can: length: refactor frame lengths definition to add size in bits
Date: Tue, 30 May 2023 21:49:39 +0200 [thread overview]
Message-ID: <ZHZTUw9HWE10CUn0@corigine.com> (raw)
In-Reply-To: <CAMZ6RqK2vr0KRq76UNOSKzHMEfhz1YPFdg7CdQJqq4pBH3hj5w@mail.gmail.com>
On Wed, May 31, 2023 at 02:29:43AM +0900, Vincent MAILHOL wrote:
> On Wed. 31 May 2023 at 00:56, Simon Horman <simon.horman@corigine.com> wrote:
> > On Tue, May 30, 2023 at 11:46:37PM +0900, Vincent Mailhol wrote:
...
> > > +/**
> > > + * can_bitstuffing_len() - Calculate the maximum length with bitsuffing
> > > + * @bitstream_len: length of a destuffed bit stream
> >
> > Hi Vincent,
> >
> > it looks like an editing error has crept in here:
> >
> > s/bitstream_len/destuffed_len/
>
> Doh! Thanks for picking this up.
>
> I already prepared a v4 locally. Before sending it, I will wait one
> day to see if there are other comments.
Thanks, sounds good.
--
pw-bot: cr
next prev parent reply other threads:[~2023-05-30 19:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 15:55 [PATCH] can: length: add definitions for frame lengths in bits Vincent Mailhol
2023-05-08 8:54 ` Thomas.Kopp
2023-05-08 12:14 ` Marc Kleine-Budde
2023-05-09 4:16 ` Vincent MAILHOL
2023-05-09 6:43 ` Marc Kleine-Budde
2023-05-09 8:14 ` Vincent MAILHOL
2023-05-09 6:19 ` Thomas.Kopp
2023-05-08 12:20 ` Marc Kleine-Budde
2023-05-09 4:58 ` Vincent MAILHOL
2023-05-09 7:12 ` Thomas.Kopp
2023-05-09 8:06 ` Vincent MAILHOL
2023-05-23 6:52 ` [PATCH v2 0/3] can: length: fix definitions and add bit length calculation Vincent Mailhol
2023-05-23 6:52 ` [PATCH v2 1/3] can: length: fix bitstuffing count Vincent Mailhol
2023-05-23 6:52 ` [PATCH v2 2/3] can: length: fix description of the RRS field Vincent Mailhol
2023-05-23 6:52 ` [PATCH v2 3/3] can: length: refactor frame lengths definition to add size in bits Vincent Mailhol
2023-05-23 7:13 ` Vincent MAILHOL
2023-05-23 11:14 ` Simon Horman
2023-05-30 14:46 ` [PATCH v3 0/3] can: length: fix definitions and add bit length calculation Vincent Mailhol
2023-05-30 14:46 ` [PATCH v3 1/3] can: length: fix bitstuffing count Vincent Mailhol
2023-05-30 14:46 ` [PATCH v3 2/3] can: length: fix description of the RRS field Vincent Mailhol
2023-05-30 14:46 ` [PATCH v3 3/3] can: length: refactor frame lengths definition to add size in bits Vincent Mailhol
2023-05-30 15:51 ` Simon Horman
2023-05-30 17:29 ` Vincent MAILHOL
2023-05-30 19:49 ` Simon Horman [this message]
2023-05-31 9:45 ` Vincent MAILHOL
2023-06-01 10:31 ` Thomas.Kopp
2023-06-01 11:00 ` Vincent MAILHOL
2023-06-01 11:26 ` Thomas.Kopp
2023-06-01 16:56 ` [PATCH v4 0/3] can: length: fix definitions and add bit length calculation Vincent Mailhol
2023-06-01 16:56 ` [PATCH v4 1/3] can: length: fix bitstuffing count Vincent Mailhol
2023-06-01 16:56 ` [PATCH v4 2/3] can: length: fix description of the RRS field Vincent Mailhol
2023-06-01 16:56 ` [PATCH v4 3/3] can: length: refactor frame lengths definition to add size in bits Vincent Mailhol
2023-06-11 2:57 ` [PATCH v5 0/3] can: length: fix definitions and add bit length calculation Vincent Mailhol
2023-06-11 2:57 ` [PATCH v5 1/3] can: length: fix bitstuffing count Vincent Mailhol
2023-06-11 2:57 ` [PATCH v5 2/3] can: length: fix description of the RRS field Vincent Mailhol
2023-06-11 2:57 ` [PATCH v5 3/3] can: length: refactor frame lengths definition to add size in bits Vincent Mailhol
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=ZHZTUw9HWE10CUn0@corigine.com \
--to=simon.horman@corigine.com \
--cc=Thomas.Kopp@microchip.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=marex@denx.de \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.