From: davem@davemloft.net (David Miller)
Subject: [PATCH 1/3] net/utils: Introduce inet_addr_is_any
Date: Tue, 06 Feb 2018 09:42:53 -0500 (EST) [thread overview]
Message-ID: <20180206.094253.2191113540764519816.davem@davemloft.net> (raw)
In-Reply-To: <20180206094432.12761-2-sagi@grimberg.me>
From: Sagi Grimberg <sagi@grimberg.me>
Date: Tue, 6 Feb 2018 11:44:30 +0200
> + if (!memcmp(in6->sin6_addr.s6_addr,
> + in6_any.sin6_addr.s6_addr, 16))
Please indent this properly.
When a function call spans multiple lines, the second and subsequent
lines of that call must be indented precisely to the column that follows
the openning parenthesis of that call.
You must use the appropriate number of TAB then SPACE characters
necessary to achieve this.
Thank you.
next prev parent reply other threads:[~2018-02-06 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 9:44 [PATCH 0/3] Commonise address any check Sagi Grimberg
2018-02-06 9:44 ` [PATCH 1/3] net/utils: Introduce inet_addr_is_any Sagi Grimberg
2018-02-06 14:42 ` David Miller [this message]
2018-02-06 15:27 ` Bart Van Assche
2018-02-06 9:44 ` [PATCH 2/3] nvmet: don't return "any" ip address in discovery log page Sagi Grimberg
2018-02-06 10:36 ` Johannes Thumshirn
2018-02-06 9:44 ` [PATCH 3/3] iscsi-target: use common inet_addr_is_any Sagi Grimberg
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=20180206.094253.2191113540764519816.davem@davemloft.net \
--to=davem@davemloft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox