public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: michael.christie@oracle.com
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
	linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
	martin.petersen@oracle.com
Cc: hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH 1/3] target/iscsi: rename iscsi_cmd to iscsit_cmd
Date: Wed, 4 May 2022 08:00:29 -0700	[thread overview]
Message-ID: <b330fbf7-41b4-6a67-38c4-eea514ebfadb@oracle.com> (raw)
In-Reply-To: <20220428092939.36768-1-mgurtovoy@nvidia.com>

On 4/28/22 2:29 AM, Max Gurtovoy wrote:
> The structure iscsi_cmd naming is used by the iscsi initiator driver.
> Rename the target cmd to iscsit_cmd to have more readable code.
> 
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
>  drivers/infiniband/ulp/isert/ib_isert.c       |  64 ++++----
>  drivers/infiniband/ulp/isert/ib_isert.h       |   2 +-
>  drivers/target/iscsi/cxgbit/cxgbit.h          |   8 +-
>  drivers/target/iscsi/cxgbit/cxgbit_ddp.c      |   4 +-
>  drivers/target/iscsi/cxgbit/cxgbit_target.c   |  34 ++--
>  drivers/target/iscsi/iscsi_target.c           | 150 +++++++++---------
>  drivers/target/iscsi/iscsi_target.h           |  14 +-
>  drivers/target/iscsi/iscsi_target_configfs.c  |  14 +-
>  .../target/iscsi/iscsi_target_datain_values.c |  18 +--
>  .../target/iscsi/iscsi_target_datain_values.h |  12 +-
>  drivers/target/iscsi/iscsi_target_device.c    |   2 +-
>  drivers/target/iscsi/iscsi_target_device.h    |   4 +-
>  drivers/target/iscsi/iscsi_target_erl0.c      |  30 ++--
>  drivers/target/iscsi/iscsi_target_erl0.h      |   8 +-
>  drivers/target/iscsi/iscsi_target_erl1.c      |  42 ++---
>  drivers/target/iscsi/iscsi_target_erl1.h      |  20 +--
>  drivers/target/iscsi/iscsi_target_erl2.c      |  20 +--
>  drivers/target/iscsi/iscsi_target_erl2.h      |   8 +-
>  drivers/target/iscsi/iscsi_target_nego.c      |   2 +-
>  .../target/iscsi/iscsi_target_seq_pdu_list.c  |  34 ++--
>  .../target/iscsi/iscsi_target_seq_pdu_list.h  |  10 +-
>  drivers/target/iscsi/iscsi_target_tmr.c       |  38 ++---
>  drivers/target/iscsi/iscsi_target_tmr.h       |   8 +-
>  drivers/target/iscsi/iscsi_target_util.c      |  66 ++++----
>  drivers/target/iscsi/iscsi_target_util.h      |  48 +++---
>  include/target/iscsi/iscsi_target_core.h      |  34 ++--
>  include/target/iscsi/iscsi_transport.h        |  92 +++++------
>  27 files changed, 393 insertions(+), 393 deletions(-)


Reviewed-by: Mike Christie <michael.christie@oracle.com>

  parent reply	other threads:[~2022-05-04 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  9:29 [PATCH 1/3] target/iscsi: rename iscsi_cmd to iscsit_cmd Max Gurtovoy
2022-04-28  9:29 ` [PATCH 2/3] target/iscsi: rename iscsi_conn to iscsit_conn Max Gurtovoy
2022-05-04 15:00   ` michael.christie
2022-04-28  9:29 ` [PATCH 3/3] target/iscsi: rename iscsi_session to iscsit_session Max Gurtovoy
2022-05-04 15:01   ` michael.christie
2022-05-04 15:00 ` michael.christie [this message]
2022-05-11  2:32 ` [PATCH 1/3] target/iscsi: rename iscsi_cmd to iscsit_cmd Martin K. Petersen
2022-05-17  2:16 ` Martin K. Petersen

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=b330fbf7-41b4-6a67-38c4-eea514ebfadb@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=sagi@grimberg.me \
    --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