linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Christie <mchristi@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
	seroyer@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org, "Bryant G. Ly" <bgly@us.ibm.com>
Subject: Re: [PATCH v4 0/5] tcmu: Add Type of reconfig into netlink
Date: Fri, 30 Jun 2017 12:51:01 -0500	[thread overview]
Message-ID: <59568F85.8010702@redhat.com> (raw)
In-Reply-To: <497e60b0-5ade-b266-af5b-e47a013369b9@redhat.com>

On 06/30/2017 11:58 AM, Mike Christie wrote:
> On 06/30/2017 02:31 AM, Nicholas A. Bellinger wrote:
>> Hey MNC,
>>
>> On Mon, 2017-06-12 at 01:43 -0500, Mike Christie wrote:
>>> On 06/11/2017 04:02 PM, Mike Christie wrote:
>>>> On 06/09/2017 01:11 AM, Nicholas A. Bellinger wrote:
>>>>> Hi Bryant & Co,
>>>>>
>>>>> On Tue, 2017-06-06 at 09:28 -0500, Bryant G. Ly wrote:
>>>>>> From: "Bryant G. Ly" <bgly@us.ibm.com>
>>>>>>
>>>>>> This patch consists of adding a netlink to allow for reconfiguration
>>>>>> of a device in tcmu.
>>>>>>
>>>>>> It also changes and adds some attributes that are reconfigurable:
>>>>>> write_cache, device size, and device path.
>>>>>>
>>>>>> V2 - Fixes kfree in tcmu: Make dev_config configurable
>>>>>> V3 - Fixes spelling error
>>>>>> V4 - change strcpy to strlcpy for tcmu_dev_path_store and move
>>>>>>      tcmu_reconfig_type into target_core_user.h
>>>>>>
>>>>>>
>>>>>> Bryant G. Ly (5):
>>>>>>   tcmu: Support emulate_write_cache
>>>>>>   tcmu: Add netlink for device reconfiguration
>>>>>>   tcmu: Make dev_size configurable via userspace
>>>>>>   tcmu: Make dev_config configurable
>>>>>>   tcmu: Add Type of reconfig into netlink
>>>>>>
>>>>>>  drivers/target/target_core_user.c     | 152 ++++++++++++++++++++++++++++++++--
>>>>>>  include/uapi/linux/target_core_user.h |   9 ++
>>>>>>  2 files changed, 155 insertions(+), 6 deletions(-)
>>>>>>
>>>>>
>>>>> AFAICT, it looks like all of the review comments have been addressed in
>>>>> -v4.
>>>>>
>>>>> Applied to target-pending/for-next, with MNC's (pseudo) Reviewed-by's
>>>>> added for #3-#5.
>>>>>
>>>>> Please let me know if anything else needs to be changed.
>>>>>
>>>>
>>>> The patches look ok. Thanks. Could you just merge the attached patch
>>>> into "[PATCH v4 5/5] tcmu: Add Type of reconfig into netlink" or into
>>>> the patchset after it? It just makes some of the names a little less
>>>> generic and only returns the reconfig attr for reconfig commands.
>>>>
>>>
>>> Actually Nick, do not merge the last patch. I have a lot more fixes/changes.
>>>
>>> Bryant, could you test and adapt your userspace patches for the attached
>>> patch build over Nicks for-next branch.
>>>
>>> Basically, the patch just has use pass the value being reconfigured with
>>> the netlink event. Along the way, it fixes a couple bugs.
>>>
>>> Nick, when we have tested the patch, then I can submit as a formal
>>> patchset, or you can fold into the existing patches or whatever you prefer.
>>>
>>
>> Looking at merging your -v4 patches series here next:
>>
>> [PATCH V4 00/10] target/tcmu: make tcmu netlink ops sync
>> http://www.spinics.net/lists/target-devel/msg15706.html
>>
>> Do you still want me to drop the patch from Bryant below as mentioned
>> earlier..?
> 
> Hey,
> 
> First, sorry for the mess of comments/patches in various threads.
> 
> No need to drop it. The first patch:

Oh wait. Just to make sure I understood you correctly. I meant you do
not need to drop any of Bryant's patches. But, the patches:

https://www.spinics.net/lists/target-devel/msg15593.html
https://www.spinics.net/lists/target-devel/msg15595.html

I sent in Bryant's thread "[PATCH v4 0/5] tcmu: Add Type of reconfig
into netlink" do not need to be applied. The patch "[PATCH 01/10] tcmu:
reconfigure netlink attr changes" in my patchset you referenced "[PATCH
V4 00/10] target/tcmu: make tcmu netlink ops sync" is the correct up to
date patch.


> 
> [PATCH 01/10] tcmu: reconfigure netlink attr changes
> 
> in the thread you referenced above just fixes the stuff that needed to
> be fixed.
> 
> 
>>
>> tcmu: Add Type of reconfig into netlink
>> https://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git/commit/?h=for-next&id=28d44b983000754677155e46f6bdafc7b4d84213
>>
> 

      reply	other threads:[~2017-06-30 17:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 14:28 [PATCH v4 0/5] tcmu: Add Type of reconfig into netlink Bryant G. Ly
2017-06-06 14:28 ` [PATCH v4 1/5] tcmu: Support emulate_write_cache Bryant G. Ly
2017-06-06 14:28 ` [PATCH v4 2/5] tcmu: Add netlink for device reconfiguration Bryant G. Ly
2017-06-06 14:28 ` [PATCH v4 3/5] tcmu: Make dev_size configurable via userspace Bryant G. Ly
2017-06-06 14:28 ` [PATCH v4 4/5] tcmu: Make dev_config configurable Bryant G. Ly
2017-06-06 14:28 ` [PATCH v4 5/5] tcmu: Add Type of reconfig into netlink Bryant G. Ly
2017-06-09  6:11 ` [PATCH v4 0/5] " Nicholas A. Bellinger
2017-06-11 21:02   ` Mike Christie
2017-06-12  6:43     ` Mike Christie
2017-06-30  7:31       ` Nicholas A. Bellinger
2017-06-30 16:58         ` Mike Christie
2017-06-30 17:51           ` Mike Christie [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=59568F85.8010702@redhat.com \
    --to=mchristi@redhat.com \
    --cc=bgly@us.ibm.com \
    --cc=bryantly@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=seroyer@linux.vnet.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).