From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Kanchan Joshi <joshi.k@samsung.com>, "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"joshiiitr@gmail.com" <joshiiitr@gmail.com>
Subject: Re: [PATCH 1/2] block: introduce and export blk_rq_map_user_vec
Date: Fri, 28 Jan 2022 09:04:05 +0000 [thread overview]
Message-ID: <0dfe7d55-6a1a-ca12-0bd3-7be0475d03ea@nvidia.com> (raw)
In-Reply-To: <20220127082536.7243-2-joshi.k@samsung.com>
On 1/27/22 12:25 AM, Kanchan Joshi wrote:
> External email: Use caution opening links or attachments
>
>
> Similiar to blk_rq_map_user except that it operates on iovec.
> This is a prep patch.
>
> Signed-off-by: Kanchan Joshi <joshi.k@samsung.com>
> Signed-off-by: Anuj Gupta <anuj20.g@samsung.com>
> ---
Did you run checkpatch.pl ?
next prev parent reply other threads:[~2022-01-28 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220127083033epcas5p3ce9565e4b5e21e897571e48e73e4f9af@epcas5p3.samsung.com>
2022-01-27 8:25 ` [PATCH 0/2] nvme-passthru with vectored-io Kanchan Joshi
[not found] ` <CGME20220127083034epcas5p4aaafaf1f40c21a383e985d6f6568cbef@epcas5p4.samsung.com>
2022-01-27 8:25 ` [PATCH 1/2] block: introduce and export blk_rq_map_user_vec Kanchan Joshi
2022-01-27 9:27 ` Christoph Hellwig
2022-01-27 14:38 ` Kanchan Joshi
2022-01-28 9:04 ` Chaitanya Kulkarni [this message]
[not found] ` <CGME20220127083035epcas5p3e3760849513fb7939757f4e6678405a0@epcas5p3.samsung.com>
2022-01-27 8:25 ` [PATCH 2/2] nvme: add vectored-io support for user passthru Kanchan Joshi
2022-01-27 9:29 ` Christoph Hellwig
2022-01-27 14:43 ` Kanchan Joshi
2022-01-28 9:08 ` Chaitanya Kulkarni
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=0dfe7d55-6a1a-ca12-0bd3-7be0475d03ea@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.