[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <17154add-faf8-4150-bc07-57e07b5c9ea7@kernel.dk>
Date: Tue, 18 Mar 2025 07:19:32 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Sidong Yang <sidong.yang@...iosa.ai>,
Pavel Begunkov <asml.silence@...il.com>
Cc: Josef Bacik <josef@...icpanda.com>, David Sterba <dsterba@...e.com>,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
io-uring@...r.kernel.org
Subject: Re: [RFC PATCH v4 0/5] introduce io_uring_cmd_import_fixed_vec
On 3/18/25 1:41 AM, Sidong Yang wrote:
> On Tue, Mar 18, 2025 at 07:30:51AM +0000, Pavel Begunkov wrote:
>> On 3/17/25 13:57, Sidong Yang wrote:
>>> This patche series introduce io_uring_cmd_import_vec. With this function,
>>> Multiple fixed buffer could be used in uring cmd. It's vectored version
>>> for io_uring_cmd_import_fixed(). Also this patch series includes a usage
>>> for new api for encoded read/write in btrfs by using uring cmd.
>>
>> You're vigorously ignoring the previous comment, you can't stick
>> your name to my patches and send them as your own, that's not
>> going to work. git format-patch and other tools allow to send
>> other's patches in the same patch set without mutilating them.
>
> I'm just not familiar with this. That wasn't my intention. Sorry, Your
> patches will be included without modification.
Assuming these are from a git branch you have, just ensure they are
committed with Pavel as the author, and git send-email will do the right
thing when sending out the patch.
--
Jens Axboe
Powered by blists - more mailing lists