From: Sagi Grimberg <sagi@grimberg.me>
To: Ming Lin <mlin@kernel.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v3 1/5] scsi: replace "scsi_data_buffer" with "sg_table" in SG functions
Date: Tue, 12 Apr 2016 13:36:25 +0300 [thread overview]
Message-ID: <570CCFA9.4010902@grimberg.me> (raw)
In-Reply-To: <1459806491-16428-2-git-send-email-mlin@kernel.org>
> From: Ming Lin <ming.l@ssi.samsung.com>
>
> Replace parameter "struct scsi_data_buffer" with "struct sg_table" in
> SG alloc/free functions to make them generic.
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Ming Lin <ming.l@ssi.samsung.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2016-04-12 10:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 21:48 [PATCH v3 0/5] mempool based chained scatterlist alloc/free api Ming Lin
2016-04-04 21:48 ` [PATCH v3 1/5] scsi: replace "scsi_data_buffer" with "sg_table" in SG functions Ming Lin
2016-04-12 10:36 ` Sagi Grimberg [this message]
2016-04-04 21:48 ` [PATCH v3 2/5] scsi: replace "mq" with "first_chunk" " Ming Lin
2016-04-12 10:36 ` Sagi Grimberg
2016-04-04 21:48 ` [PATCH v3 3/5] scsi: rename SG related struct and functions Ming Lin
2016-04-12 10:40 ` Sagi Grimberg
2016-04-04 21:48 ` [PATCH v3 4/5] scsi: rename SCSI_MAX_{SG, SG_CHAIN}_SEGMENTS Ming Lin
2016-04-05 14:55 ` Tejun Heo
2016-04-11 5:20 ` Ming Lin
2016-04-11 21:34 ` Martin K. Petersen
2016-04-11 22:04 ` Ming Lin
2016-04-12 2:43 ` Bart Van Assche
2016-04-12 10:42 ` Sagi Grimberg
2016-04-12 10:34 ` Sagi Grimberg
2016-04-12 22:00 ` Martin K. Petersen
2016-04-04 21:48 ` [PATCH v3 5/5] lib: scatterlist: move SG pool code from SCSI driver to lib/sg_pool.c Ming Lin
2016-04-12 10:44 ` Sagi Grimberg
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=570CCFA9.4010902@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mlin@kernel.org \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).