From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Stefan Wahren <stefan.wahren@i2se.com>, yegorslists@googlemail.com
Cc: linux-can@vger.kernel.org, mkl@pengutronix.de
Subject: Re: [PATCH v3] slcand: add slcan_attach and UART settings
Date: Sun, 15 Sep 2013 22:11:41 +0200 [thread overview]
Message-ID: <5236147D.8020200@hartkopp.net> (raw)
In-Reply-To: <5232F733.2040707@i2se.com>
On 13.09.2013 13:29, Stefan Wahren wrote:
> Hello Yegor,
>
> Am 13.09.2013 12:11, schrieb yegorslists@googlemail.com:
>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>
>> slcand takes settings known from slcan_attach to configure CAN
>> interface, like open/close channel, set bitrate etc (Oliver Hartkopp).
>>
>> In addition -S option sets UART's baudrate (Yegor Yefremov).
>>
>> This way slcand combines three autilities in one: old slcand,
>> slcan_attach and stty.
>>
>> Example: slcand -o -s8 -S 3000000 ttyUSB0
>>
>> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
>> CC: stefan.wahren@i2se.com
>> CC: socketcan@hartkopp.net
>> CC: mkl@pengutronix.de
>> ---
>> Changes since v2:
>> More style fixes as suggested by Stefan Wahren
>> Changes since v1:
>> Implement suggestions from Stefan Wahren
>> - fix style issues
>> - changed look_up_uart_speed parameter from int to long int
>> - look_up_uart_speed return value will be checked for unsupported baudrates
>> slcand.c | 297
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++---------
>> 1 files changed, 255 insertions(+), 42 deletions(-)
>>
> okay, looks good to me.
>
> Best regards
>
> Stefan
>
Hi all,
i applied the v3 patch to the can-utils git repo.
Thanks!
I tried linux/scripts/checkpatch.pl which provided tons of issues :-(
Therefore i fixed up the entire coding style and removed an empty statement
in the 'if (speed)' condition to make sure, that the write() statement is not
unintentionally optimized away by the compiler %-)
See changes here:
https://gitorious.org/linux-can/can-utils/commit/35d2bc1381f04e0fcc5baadf9d1ddad8db0187d3
There's still one warning left:
slcand.c: In function 'daemonize':
slcand.c:180:8: warning: variable 'dummyFile' set but not used [-Wunused-but-set-variable]
FILE *dummyFile;
^
Any suggestion?
Best regards,
Oliver
next prev parent reply other threads:[~2013-09-15 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 10:11 [PATCH v3] slcand: add slcan_attach and UART settings yegorslists
2013-09-13 11:29 ` Stefan Wahren
2013-09-15 20:11 ` Oliver Hartkopp [this message]
2013-09-16 7:14 ` Oliver Hartkopp
2013-09-17 7:22 ` Stefan Wahren
2013-09-17 12:08 ` Yegor Yefremov
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=5236147D.8020200@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=stefan.wahren@i2se.com \
--cc=yegorslists@googlemail.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;
as well as URLs for NNTP newsgroup(s).