From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ranjan Kumar <ranjan.kumar@broadcom.com>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
rajsekhar.chundru@broadcom.com, sathya.prakash@broadcom.com,
sumit.saxena@broadcom.com, chandrakanth.patil@broadcom.com,
sreekanth.reddy@broadcom.com
Subject: Re: [PATCH v1 4/6] mpi3mr: WriteSame implementation
Date: Tue, 25 Jul 2023 21:24:18 -0400 [thread overview]
Message-ID: <yq1pm4fzdmv.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230724132303.19470-5-ranjan.kumar@broadcom.com> (Ranjan Kumar's message of "Mon, 24 Jul 2023 18:53:01 +0530")
Hi Ranjan!
I am still unable to parse the indentation:
> @@ -4445,39 +4500,50 @@ static int mpi3mr_target_alloc(struct scsi_target *starget)
> starget->hostdata = scsi_tgt_priv_data;
>
> spin_lock_irqsave(&mrioc->tgtdev_lock, flags);
> -
> if (starget->channel == mrioc->scsi_device_channel) {
> tgt_dev = __mpi3mr_get_tgtdev_by_perst_id(mrioc, starget->id);
> - if (tgt_dev && !tgt_dev->is_hidden)
> - update_stgt_priv_data = true;
> - else
> + if (tgt_dev && !tgt_dev->is_hidden) {
The block starts here ^
> + scsi_tgt_priv_data->starget = starget;
> + scsi_tgt_priv_data->dev_handle = tgt_dev->dev_handle;
> + scsi_tgt_priv_data->perst_id = tgt_dev->perst_id;
> + scsi_tgt_priv_data->dev_type = tgt_dev->dev_type;
> + scsi_tgt_priv_data->tgt_dev = tgt_dev;
> + tgt_dev->starget = starget;
> + atomic_set(&scsi_tgt_priv_data->block_io, 0);
> + retval = 0;
> + if ((tgt_dev->dev_type == MPI3_DEVICE_DEVFORM_PCIE) &&
> + ((tgt_dev->dev_spec.pcie_inf.dev_info &
> + MPI3_DEVICE0_PCIE_DEVICE_INFO_TYPE_MASK) ==
> + MPI3_DEVICE0_PCIE_DEVICE_INFO_TYPE_NVME_DEVICE) &&
> + ((tgt_dev->dev_spec.pcie_inf.dev_info &
> + MPI3_DEVICE0_PCIE_DEVICE_INFO_PITYPE_MASK) !=
> + MPI3_DEVICE0_PCIE_DEVICE_INFO_PITYPE_0))
> + scsi_tgt_priv_data->dev_nvme_dif = 1;
> + scsi_tgt_priv_data->io_throttle_enabled = tgt_dev->io_throttle_enabled;
> + scsi_tgt_priv_data->wslen = tgt_dev->wslen;
> + if (tgt_dev->dev_type == MPI3_DEVICE_DEVFORM_VD)
> + scsi_tgt_priv_data->throttle_group = tgt_dev->dev_spec.vd_inf.tg;
> + } else
and ends here. ^
So either everything after "retval = 0" is incorrectly indented or it
belongs in a different scope.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-07-26 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 13:22 [PATCH v1 0/6] mpi3mr: Few Enhancements and minor fixes Ranjan Kumar
2023-07-24 13:22 ` [PATCH v1 1/6] mpi3mr: Invokes soft reset upon TSU or event ack time out Ranjan Kumar
2023-07-24 13:22 ` [PATCH v1 2/6] mpi3mr: Update MPI Headers to version 3.00.28 Ranjan Kumar
2023-07-24 13:23 ` [PATCH v1 3/6] mpi3mr: Add support for more than 1MB I/O Ranjan Kumar
2023-07-24 13:23 ` [PATCH v1 4/6] mpi3mr: WriteSame implementation Ranjan Kumar
2023-07-26 1:24 ` Martin K. Petersen [this message]
2023-07-27 17:06 ` kernel test robot
2023-07-24 13:23 ` [PATCH v1 5/6] mpi3mr: Enhance handling of devices removed after controller reset Ranjan Kumar
2023-07-24 13:23 ` [PATCH v1 6/6] mpi3mr: Update driver version to 8.5.0.0.0 Ranjan Kumar
2023-07-26 1:04 ` [PATCH v1 0/6] mpi3mr: Few Enhancements and minor fixes Martin K. Petersen
2023-07-26 10:41 ` Ranjan kumar
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=yq1pm4fzdmv.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rajsekhar.chundru@broadcom.com \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=sumit.saxena@broadcom.com \
/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