From: Martin Wilck <mwilck@suse.com>
To: Bart Van Assche <bart.vanassche@wdc.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 1/2] Allow the compiler to verify consistency of declarations and definitions
Date: Mon, 19 Mar 2018 21:07:00 +0100 [thread overview]
Message-ID: <1521490020.3798.115.camel@suse.com> (raw)
In-Reply-To: <20180319162351.28950-2-bart.vanassche@wdc.com>
On Mon, 2018-03-19 at 09:23 -0700, Bart Van Assche wrote:
> Make sure that in every source file the header file is included that
> declares the functions defined in that source file. This allows the
> compiler to detect inconsistencies between source and header files.
>
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
Reviewed-by: Martin Wilck <mwilck@suse.com>
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-03-19 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 16:23 [PATCH 0/2] Fix recently introduced inconsistencies Bart Van Assche
2018-03-19 16:23 ` [PATCH 1/2] Allow the compiler to verify consistency of declarations and definitions Bart Van Assche
2018-03-19 20:07 ` Martin Wilck [this message]
2018-05-11 18:20 ` Xose Vazquez Perez
2018-03-19 16:23 ` [PATCH 2/2] libmultipath: Fix recently introduced inconsistencies Bart Van Assche
2018-03-19 20:23 ` Martin Wilck
2018-03-19 20:27 ` [PATCH v2 " Martin Wilck
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=1521490020.3798.115.camel@suse.com \
--to=mwilck@suse.com \
--cc=bart.vanassche@wdc.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.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