From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lapi/io_uring.h: Add declaration of __kernel_rwf_t
Date: Fri, 17 Jul 2020 12:38:16 +0200 [thread overview]
Message-ID: <20200717103816.GA28835@yuki.lan> (raw)
In-Reply-To: <1eac1ed9-66dd-5141-0bc2-cc05312704c8@cn.fujitsu.com>
Hi!
> how about the follwing change
>
> +#ifdef __CHECKER__
> +#define __bitwise__ __attribute__((bitwise))
> +#else
> +#define __bitwise__
> +#endif
> +#define __bitwise __bitwise__
> +
> +#ifndef __kernel_rwf_t
> +typedef int __bitwise __kernel_rwf_t;
> +#endif
>
> Also, I think we should replace _u32 with uint32 in lapi/loop.h if we
> don't want to include linux kernel header for single use.
The whole __bitwise is used only by a sparse checker, there is no point
to include it in LTP. So we can just typedef the __kernel_rwf_t to int.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-07-17 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 4:13 [LTP] [PATCH] lapi/io_uring.h: Add declaration of __kernel_rwf_t Yang Xu
2020-07-17 7:38 ` Petr Vorel
2020-07-17 8:08 ` Petr Vorel
2020-07-17 10:32 ` Yang Xu
2020-07-17 10:38 ` Cyril Hrubis [this message]
2020-07-17 11:04 ` Petr Vorel
2020-07-17 11:29 ` Petr Vorel
2020-07-19 17:26 ` Jan Stancek
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=20200717103816.GA28835@yuki.lan \
--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