From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 2/4] lapi/socket.h: Move definitions from netstress.c
Date: Thu, 9 Nov 2017 16:17:03 +0100 [thread overview]
Message-ID: <20171109151703.GB30136@rei> (raw)
In-Reply-To: <20171109113947.24609-3-pvorel@suse.cz>
Hi!
> #ifndef SOCK_CLOEXEC
> -# define SOCK_CLOEXEC 02000000
> +#define SOCK_CLOEXEC 02000000
> +#endif
FYI the prefered way how to indent innner macros are spaces after the
hash #.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-11-09 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 11:39 [LTP] [RFC PATCH 0/4] Add headers in lapi Petr Vorel
2017-11-09 11:39 ` [LTP] [RFC PATCH 1/4] lapi: Add lapi/tcp.h with definitions moved from netstress.c Petr Vorel
2017-11-09 11:39 ` [LTP] [RFC PATCH 2/4] lapi/socket.h: Move definitions " Petr Vorel
2017-11-09 15:17 ` Cyril Hrubis [this message]
2017-11-10 13:14 ` Alexey Kodanev
2017-11-21 11:45 ` Petr Vorel
2017-11-09 11:39 ` [LTP] [RFC PATCH 3/4] lapi: Add lapi/in.h with definition moved " Petr Vorel
2017-11-09 15:18 ` Cyril Hrubis
2017-11-09 16:05 ` Petr Vorel
2017-11-21 11:51 ` Petr Vorel
2017-11-09 11:39 ` [LTP] [RFC PATCH 4/4] lapi: Add lapi/dccp.h " Petr Vorel
2017-11-09 14:54 ` [LTP] [RFC PATCH 0/4] Add headers in lapi Cyril Hrubis
2017-11-09 15:49 ` Petr Vorel
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=20171109151703.GB30136@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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