From: Nicholas Mc Guire <der.herr@hofr.at>
To: Prasad Gondi <pgondi@vmware.com>
Cc: Nicholas Mc Guire <hofrat@osadl.org>,
Vasu Dev <vasu.dev@intel.com>,
"fcoe-devel@open-fcoe.org" <fcoe-devel@open-fcoe.org>,
"James E.J. Bottomley" <JBottomley@odin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Open-FCoE] [PATCH] scsi: fix Wunused-but-set-variable buildwarning
Date: Fri, 15 May 2015 09:14:15 +0200 [thread overview]
Message-ID: <20150515071415.GC24293@opentech.at> (raw)
In-Reply-To: <1488e7d0337944d98996c115cd0baefc@EX13-MBX-026.vmware.com>
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.
> Once we clear that out we can see whether this change make sense?
>
yup - many thanks !
hofrat
next prev parent reply other threads:[~2015-05-15 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 18:12 [PATCH] scsi: fix Wunused-but-set-variable buildwarning Nicholas Mc Guire
[not found] ` <1431627166-12729-1-git-send-email-hofrat-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2015-05-14 22:39 ` vasu.dev-VuQAYsv1563Yd54FQh9/CA
2015-05-14 23:24 ` [Open-FCoE] " Prasad Gondi
2015-05-15 7:14 ` Nicholas Mc Guire [this message]
2015-05-15 17:09 ` vasu.dev
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=20150515071415.GC24293@opentech.at \
--to=der.herr@hofr.at \
--cc=JBottomley@odin.com \
--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 \
--cc=vasu.dev@intel.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