From: Stefan Wahren <stefan.wahren@i2se.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: yegorslists@googlemail.com, linux-can@vger.kernel.org,
mkl@pengutronix.de
Subject: Re: [PATCH v3] slcand: add slcan_attach and UART settings
Date: Tue, 17 Sep 2013 09:22:42 +0200 [thread overview]
Message-ID: <52380342.5060408@i2se.com> (raw)
In-Reply-To: <5236AFCC.1090909@hartkopp.net>
Am 16.09.2013 09:14, schrieb Oliver Hartkopp:
> On 15.09.2013 22:11, Oliver Hartkopp wrote:
>
>> 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;
>> ^
>>
> Fixed :-)
>
> BR,
> Oliver
>
Thank you Oliver.
Best Regards
Stefan
next prev parent reply other threads:[~2013-09-17 7:23 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
2013-09-16 7:14 ` Oliver Hartkopp
2013-09-17 7:22 ` Stefan Wahren [this message]
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=52380342.5060408@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--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).