mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "vasu.dev@linux.intel.com" <vasu.dev@linux.intel.com>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Prasad Gondi <pgondi@vmware.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"James E.J. Bottomley" <JBottomley@odin.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Nicholas Mc Guire <hofrat@osadl.org>,
	"fcoe-devel@open-fcoe.org" <fcoe-devel@open-fcoe.org>
Subject: Re: [Open-FCoE] [PATCH] scsi: fix Wunused-but-set-variable buildwarning
Date: Fri, 15 May 2015 10:09:33 -0700	[thread overview]
Message-ID: <1431709773.4358.14.camel@lin-nd1-054.jf.intel.com> (raw)
In-Reply-To: <20150515071415.GC24293@opentech.at>

On Fri, 2015-05-15 at 09:14 +0200, Nicholas Mc Guire wrote:
> On Thu, 14 May 2015, Prasad Gondi wrote:
> 
> > It seems like     rpriv is used to set the fsp->tgt_flags originally
> > 
> > >   fsp->tgt_flags = rpriv->flags 
> > 
> > And fsp->tgt_flags are used in "fc_fcp_cmd_send" like this
> > 
> >         setup_timer(&fsp->timer, fc_fcp_timeout, (unsigned long)fsp);
> >         if (rpriv->flags & FC_RP_FLAGS_REC_SUPPORTED)
> >                 fc_fcp_timer_set(fsp, get_fsp_rec_tov(fsp));
> > 
> > Main purpose of this flags used is to set the correct TimeOut Value for fc_fcp_timer. 
> > 
> > So is the removal of the "fsp->tgt_flags = rpriv->flags" in fc_queuecommand() is intentional? Or by mistake?
> > 
> thats something I can't say - but the commit message indicated that the
> removal of tgt_flags was intentional.
> 

It was intentional and good cleanup since now rpriv->flags is used
directly with that change instead of storing in fsp->tgt_flags as it was
before.

> > Once we clear that out we can see whether this change make sense?
> >

Anycase the patch under discussion is straight forward clean up patch
since it just removes a local stack variable which is not used.

Thanks,
Vasu


  reply	other threads:[~2015-05-15 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 18:12 Nicholas Mc Guire
2015-05-14 22:39 ` [Open-FCoE] " vasu.dev
2015-05-14 23:24 ` Prasad Gondi
2015-05-15  7:14   ` Nicholas Mc Guire
2015-05-15 17:09     ` vasu.dev [this message]
2015-05-15 17:12       ` Prasad Gondi

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=1431709773.4358.14.camel@lin-nd1-054.jf.intel.com \
    --to=vasu.dev@linux.intel.com \
    --cc=JBottomley@odin.com \
    --cc=der.herr@hofr.at \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=hofrat@osadl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pgondi@vmware.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

all inboxes | Powered by JetHome®