From: Max Staudt <max@enpas.org>
To: Vincent Mailhol <vincent.mailhol@gmail.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Oliver Neukum <oneukum@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] can, tty: can327 CAN/ldisc driver for ELM327 based OBD-II adapters
Date: Fri, 13 May 2022 20:59:07 +0200 [thread overview]
Message-ID: <20220513205907.6d5473ff.max@enpas.org> (raw)
In-Reply-To: <CAMZ6RqKjGJyOPCQvS95ZUc6UrgaFzjunRhU=10biAAWYT_V_ZQ@mail.gmail.com>
On Fri, 13 May 2022 15:31:20 +0900
Vincent Mailhol <vincent.mailhol@gmail.com> wrote:
> On Fri. 13 May 2022 at 11:38, Vincent Mailhol
> <vincent.mailhol@gmail.com> wrote: [...]
> > > + case ELM327_STATE_RECEIVING:
> > > + /* Find <CR> delimiting feedback lines. */
> > > + for (len = 0;
> > > + (len < elm->rxfill) && (elm->rxbuf[len] !=
> > > '\r');
> > > + len++) {
> > > + /* empty loop */
> >
> > Question of taste but would prefer a while look with the len++ in
> > the body (if you prefer to do as above, no need to argue, just keep
> > it like it is).
>
> Actually, what about this?
>
> len = strnchr(elm->rxbuf, elm->rxfill, '\r');
Actually I'd use memchr() if anything, but not really here. I do end up
using the actual index. And since both strchr() and mrmchr() return
pointers, I'd rather avoid them because I prefer to use indices
whenever possible.
Max
next prev parent reply other threads:[~2022-05-13 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 18:29 [PATCH v6] can, tty: can327 CAN/ldisc driver for ELM327 based OBD-II adapters Max Staudt
2022-05-13 2:38 ` Vincent Mailhol
2022-05-13 6:31 ` Vincent Mailhol
2022-05-13 18:59 ` Max Staudt [this message]
2022-05-14 3:14 ` Vincent Mailhol
2022-05-14 11:11 ` Max Staudt
2022-05-14 12:24 ` Vincent Mailhol
2022-05-13 11:46 ` Marc Kleine-Budde
2022-05-13 11:52 ` Marc Kleine-Budde
2022-05-13 12:14 ` Vincent Mailhol
2022-05-14 11:04 ` Max Staudt
2022-05-14 12:10 ` Vincent Mailhol
2022-05-18 16:24 ` Vincent Mailhol
2022-05-18 16:31 ` 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=20220513205907.6d5473ff.max@enpas.org \
--to=max@enpas.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=oneukum@suse.com \
--cc=vincent.mailhol@gmail.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 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.