Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     hch@infradead.org, Vasily Averin <vasily.averin@linux.dev>
Cc:     rostedt@goodmis.org, kernel@openvz.org,
        linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
        mingo@redhat.com, asml.silence@gmail.com
In-Reply-To: <6f009241-a63f-ae43-a04b-62841aaef293@openvz.org>
References: <2eb22fb3-40cc-48f6-8ba9-5faeae0b43ff@kernel.dk> <6f009241-a63f-ae43-a04b-62841aaef293@openvz.org>
Subject: Re: [PATCH v3] io_uring: fix incorrect __kernel_rwf_t cast
Message-Id: <165298490113.98310.14692453666034246336.b4-ty@kernel.dk>
Date:   Thu, 19 May 2022 12:28:21 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

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