[PATCHSET,0/2] Cleanup read/write prep handling

Message ID	20231106144844.71910-1-axboe@kernel.dk (mailing list archive)
Headers	show Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8A6C428DAD for <io-uring@vger.kernel.org>; Mon, 6 Nov 2023 14:50:09 +0000 (UTC) From: Jens Axboe <axboe@kernel.dk> To: io-uring@vger.kernel.org Cc: dyudaken@gmail.com Subject: [PATCHSET 0/2] Cleanup read/write prep handling Date: Mon, 6 Nov 2023 07:47:48 -0700 Message-ID: <20231106144844.71910-1-axboe@kernel.dk> Precedence: bulk MIME-Version: 1.0 Content-Transfer-Encoding: 8bit
Series	Cleanup read/write prep handling \| expand [PATCHSET,0/2] Cleanup read/write prep handling [1/2] io_uring/rw: add separate prep handler for readv/writev [2/2] io_uring/rw: add separate prep handler for fixed read/write

Message ID

20231106144844.71910-1-axboe@kernel.dk (mailing list archive)

Headers

From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: dyudaken@gmail.com
Subject: [PATCHSET 0/2] Cleanup read/write prep handling
Date: Mon,  6 Nov 2023 07:47:48 -0700
Message-ID: <20231106144844.71910-1-axboe@kernel.dk>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Series

Cleanup read/write prep handling | expand

Hi, Rather than have opcode checking in the generic read/write prep handler, add separate prep handlers for the opcodes that need special attention. No functional changes intended in these patches, just a cleanup to make it easier to read/follow.