We can easily remove the tgt_flags from fc_fcp_pkt struct
and use rpriv->tgt_flags directly.

Signed-off-by: John Fastabend <[email protected]>
---

 drivers/scsi/libfc/fc_fcp.c |    4 +---
 include/scsi/libfc.h        |    2 --
 2 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/drivers/scsi/libfc/fc_fcp.c b/drivers/scsi/libfc/fc_fcp.c
index f0911b0..3eed06e 100644
--- a/drivers/scsi/libfc/fc_fcp.c
+++ b/drivers/scsi/libfc/fc_fcp.c
@@ -1151,7 +1151,7 @@ static int fc_fcp_cmd_send(struct fc_lport *lport, struct 
fc_fcp_pkt *fsp,
 
        setup_timer(&fsp->timer, fc_fcp_timeout, (unsigned long)fsp);
        fc_fcp_timer_set(fsp,
-                        (fsp->tgt_flags & FC_RP_FLAGS_REC_SUPPORTED) ?
+                        (rpriv->flags & FC_RP_FLAGS_REC_SUPPORTED) ?
                         rpriv->e_d_tov : rec_tov);
 unlock:
        fc_fcp_unlock_pkt(fsp);
@@ -1872,8 +1872,6 @@ int fc_queuecommand(struct scsi_cmnd *sc_cmd, void 
(*done)(struct scsi_cmnd *))
        }
        put_cpu();
 
-       fsp->tgt_flags = rpriv->flags;
-
        init_timer(&fsp->timer);
        fsp->timer.data = (unsigned long)fsp;
 
diff --git a/include/scsi/libfc.h b/include/scsi/libfc.h
index f986ab7..1463660 100644
--- a/include/scsi/libfc.h
+++ b/include/scsi/libfc.h
@@ -263,7 +263,6 @@ struct fc_seq_els_data {
  * struct fc_fcp_pkt - FCP request structure (one for each scsi_cmnd request)
  * @lp:              The associated local port
  * @state:           The state of the I/O
- * @tgt_flags:       Target's flags
  * @ref_cnt:         Reference count
  * @scsi_pkt_lock:   Lock to protect the SCSI packet (must be taken before the
  *                   host_lock if both are to be held at the same time)
@@ -298,7 +297,6 @@ struct fc_fcp_pkt {
        /* Housekeeping information */
        struct fc_lport   *lp;
        u16               state;
-       u16               tgt_flags;
        atomic_t          ref_cnt;
        spinlock_t        scsi_pkt_lock;
 

_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel

Reply via email to