From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] Sparse checks does not include other headers in include
Date: Tue, 28 Mar 2023 15:13:00 +0200 [thread overview]
Message-ID: <ZCLn3Fk26bPjm4qB@yuki> (raw)
In-Reply-To: <20230324062446.GA519460@pevik>
Hi!
> cd lib && make check-tst_device
>
> ...
> tst_device.c:78:5: warning: Symbol 'tst_find_free_loopdev' has no prototype or library ('tst_') prefix. Should it be static?
> tst_find_free_loopdev() is in include/tst_device.h. Could sparse-ltp.c take into
> consideration all files in include/ (if is trivial to do that)?
This is actually a geniune error, the tst_device.c does not include
tst_device.h. I will send a patchset to fix the issues.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-28 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 6:24 [LTP] Sparse checks does not include other headers in include Petr Vorel
2023-03-28 13:13 ` Cyril Hrubis [this message]
2023-03-28 13:17 ` 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=ZCLn3Fk26bPjm4qB@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rpalethorpe@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 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).