From: "lixiubo" <lixiubo@cmss.chinamobile.com>
To: "'Nicholas A. Bellinger'" <nab@linux-iscsi.org>
Cc: <mchristi@redhat.com>, <agrover@redhat.com>,
<iliastsi@arrikto.com>, <namei.unix@gmail.com>,
<sheng@yasker.org>, <linux-scsi@vger.kernel.org>,
<target-devel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH v6 0/2] tcmu: Dynamic growing data area support
Date: Tue, 2 May 2017 17:25:39 +0800 [thread overview]
Message-ID: <0b1c01d2c326$10d8c160$328a4420$@cmss.chinamobile.com> (raw)
In-Reply-To: <1493702720.23202.63.camel@haakon3.risingtidesystems.com>
> > Xiubo Li (2):
> > tcmu: Add dynamic growing data area feature support
> > tcmu: Add global data block pool support
> >
> > drivers/target/target_core_user.c | 598
> > ++++++++++++++++++++++++++++++--------
> > 1 file changed, 469 insertions(+), 129 deletions(-)
> >
>
> So based upon the feedback from MNC, this looks OK to merge.
>
> It looks like there is one bug as reported by MNC introduced by patch
> #1.
>
It's actually one enhancement.
> Please go ahead and post an incremental patch to address this at your
> earliest convenience.
>
And I will address this later.
Thank,
BRs
Xiubo
prev parent reply other threads:[~2017-05-02 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 6:25 lixiubo
2017-04-26 6:25 ` [PATCH v6 1/2] tcmu: Add dynamic growing data area feature support lixiubo
2017-04-30 5:48 ` Mike Christie
2017-04-30 10:22 ` [PATCH v6 1/2] tcmu: Add dynamic growing data area featuresupport Xiubo Li
2017-05-01 18:37 ` Mike Christie
2017-04-26 6:25 ` [PATCH v6 2/2] tcmu: Add global data block pool support lixiubo
2017-04-26 10:07 ` kbuild test robot
2017-04-30 7:31 ` Mike Christie
2017-04-30 11:29 ` Xiubo Li
2017-05-01 18:40 ` Mike Christie
2017-05-02 5:26 ` Nicholas A. Bellinger
2017-05-02 5:25 ` [PATCH v6 0/2] tcmu: Dynamic growing data area support Nicholas A. Bellinger
2017-05-02 9:25 ` lixiubo [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='0b1c01d2c326$10d8c160$328a4420$@cmss.chinamobile.com' \
--to=lixiubo@cmss.chinamobile.com \
--cc=agrover@redhat.com \
--cc=iliastsi@arrikto.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=namei.unix@gmail.com \
--cc=sheng@yasker.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®