From: Ilias Tsitsimpis <iliastsi@arrikto.com>
To: 李秀波 <lixiubo@cmss.chinamobile.com>
Cc: agrover@redhat.com, nab@linux-iscsi.org, mchristi@redhat.com,
shli@kernel.org, sheng@yasker.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, namei.unix@gmail.com,
bryantly@linux.vnet.ibm.com
Subject: Re: [PATCHv4 0/4] tcmu: bug fix and dynamic growing data area support
Date: Sat, 25 Mar 2017 10:57:14 +0200 [thread overview]
Message-ID: <20170325085714.e7azltvtr7b3xeio@iliastsi-m.arr> (raw)
In-Reply-To: <c28c75c3-0ab8-4320-9716-b36fc027ff50@email.android.com>
On Fri, Mar 24, 2017 at 02:45AM, 李秀波 wrote:
> IliasTsitsimpis <iliastsi@arrikto.com>写到：
> >Could you please validate the above snippet, and update your patches to
> >include it?
>
> They are actually two separate issues, but all for BIDI case.
>
> I'll merged into my patch.
Since these are two separate issues, I would create a new patch.
Also, feel free to add 'Tested-by' me to the first two patches.
--
Ilias
prev parent reply other threads:[~2017-03-25 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 8:36 [PATCHv4 0/4] tcmu: bug fix and dynamic growing data area support lixiubo
2017-03-21 8:36 ` [PATCHv4 1/4] tcmu: Fix possible overwrite of t_data_sg's last iov[] lixiubo
2017-03-21 19:39 ` Mike Christie
2017-03-21 8:36 ` [PATCHv4 2/4] tcmu: Fix wrongly calculating of the base_command_size lixiubo
2017-03-21 19:53 ` Mike Christie
2017-03-21 8:36 ` [PATCHv4 3/4] tcmu: Add dynamic growing data area feature support lixiubo
2017-03-21 8:36 ` [PATCHv4 4/4] tcmu: Add global data block pool support lixiubo
2017-03-21 19:12 ` [PATCHv4 0/4] tcmu: bug fix and dynamic growing data area support Bryant G. Ly
2017-03-23 16:02 ` Ilias Tsitsimpis
[not found] ` <c28c75c3-0ab8-4320-9716-b36fc027ff50@email.android.com>
2017-03-25 8:57 ` Ilias Tsitsimpis [this message]
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=20170325085714.e7azltvtr7b3xeio@iliastsi-m.arr \
--to=iliastsi@arrikto.com \
--cc=agrover@redhat.com \
--cc=bryantly@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lixiubo@cmss.chinamobile.com \
--cc=mchristi@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=namei.unix@gmail.com \
--cc=sheng@yasker.org \
--cc=shli@kernel.org \
--cc=target-devel@vger.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 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.