From: Jens Axboe <[email protected]>
To: [email protected], Vasily Averin <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH v3] io_uring: fix incorrect __kernel_rwf_t cast
Date: Thu, 19 May 2022 12:28:21 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 19 May 2022 17:30:49 +0300, Vasily Averin wrote:
> Currently 'make C=1 fs/io_uring.o' generates sparse warning:
>
> CHECK fs/io_uring.c
> fs/io_uring.c: note: in included file (through
> include/trace/trace_events.h, include/trace/define_trace.h, i
> nclude/trace/events/io_uring.h):
> ./include/trace/events/io_uring.h:488:1:
> warning: incorrect type in assignment (different base types)
> expected unsigned int [usertype] op_flags
> got restricted __kernel_rwf_t const [usertype] rw_flags
>
> [...]
Applied, thanks!
[1/1] io_uring: fix incorrect __kernel_rwf_t cast
commit: 0e7579ca732a39cc377e17509dda9bfc4f6ba78e
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-05-19 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 16:23 [PATCH] sparse: use force attribute for __kernel_rwf_t casts Vasily Averin
2022-05-14 20:53 ` Jens Axboe
2022-05-16 6:28 ` Christoph Hellwig
2022-05-18 9:20 ` [PATCH v2] io_uring: fix sparce warnings about " Vasily Averin
2022-05-19 7:03 ` Christoph Hellwig
2022-05-19 12:13 ` Jens Axboe
2022-05-19 14:30 ` [PATCH v3] io_uring: fix incorrect __kernel_rwf_t cast Vasily Averin
2022-05-19 18:28 ` Jens Axboe [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=165298490113.98310.14692453666034246336.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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