From: Benjamin Marzinski <bmarzins@redhat.com>
To: Funda Wang <fundawang@gmail.com>
Cc: dm-devel@lists.linux.dev, mwilck@suse.com
Subject: Re: [PATCH] multipath-tools test: add missing include for stdint.h
Date: Mon, 21 Jul 2025 16:39:02 -0400 [thread overview]
Message-ID: <aH6lZpZ-ZltVZNgj@redhat.com> (raw)
In-Reply-To: <CAOfq2QS2rh7_+rbqeDMa1gjEFht2QThnLqfes_kzwt02uafbvg@mail.gmail.com>
On Tue, Jul 22, 2025 at 01:28:33AM +0800, Funda Wang wrote:
> When building multipath-tools with cmocka 1.1.8. it produces following
> error when make test:
>
> In file included from test-log.c:6:
> test-log.c: In function '__wrap_dlog':
> test-log.c:24:20: error: 'uintptr_t' undeclared (first use in this function)
> 24 | expected = mock_ptr_type(char *);
> | ^~~~~~~~~~~~~
> test-log.c:10:1: note: 'uintptr_t' is defined in header '<stdint.h>'; did
> you forget to '#include <stdint.h>'?
> 9 | #include "debug.h"
> +++ |+#include <stdint.h>
> 10 |
> test-log.c:24:20: note: each undeclared identifier is reported only once
> for each function it appears in
> 24 | expected = mock_ptr_type(char *);
> | ^~~~~~~~~~~~~
> test-log.c:24:20: error: expected ')' before '_mock'
> 24 | expected = mock_ptr_type(char *);
> | ^~~~~~~~~~~~~
> test-log.c:24:20: note: to match this '('
> 24 | expected = mock_ptr_type(char *);
> | ^~~~~~~~~~~~~
> make[1]: *** [Makefile:74: test-log.o] Error 1
> rm parser.o.wrap dmevents.o.wrap hwtable.o.wrap uevent.o.wrap
> blacklist.o.wrap util.o.wrap
> make[1]: Leaving directory
> '/home/lkp/rpmbuild/BUILD/multipath-tools-0.9.5/tests'
> make: *** [Makefile:121: test] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.7qc9Bd (%check)
>
> The attached patch solved this issue. Thanks.
>
> GitHub pull request: https://github.com/opensvc/multipath-tools/pull/117
Looks good, but for future reference, it's easier to apply if the patch
is inline ("git format-patch" and "git send-email" will make sure it's
in the proper form. We use the same email workflow as the linux kernel,
so you can look at linux kernel patch submission instructions for
how to use git to submit patches). But thanks for the fix.
Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>
prev parent reply other threads:[~2025-07-21 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 17:28 [PATCH] multipath-tools test: add missing include for stdint.h Funda Wang
2025-07-21 20:39 ` Benjamin Marzinski [this message]
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=aH6lZpZ-ZltVZNgj@redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=fundawang@gmail.com \
--cc=mwilck@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.