From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: James.Smart@emulex.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/6] lpfc 8.1.7 : Fix failing firmware download due to mailbox delays needing to be longer
Date: Tue, 1 Aug 2006 14:20:41 +0200 [thread overview]
Message-ID: <200608011420.41752.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <1154432023.18162.13.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
James Smart wrote:
> Fix failing firmware download due to mailbox delays needing to be longer.
> /* timeout active mbox command */
> - mod_timer(&psli->mbox_tmo, jiffies + HZ * LPFC_MBOX_TMO);
> + mod_timer(&psli->mbox_tmo, (jiffies +
> + (HZ * lpfc_mbox_tmo_val(phba, mb->mbxCommand))));
> }
In linux/jiffies.h there are some functions for converting jiffies to *secs
and back which you might find useful.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-01 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 11:33 [PATCH 2/6] lpfc 8.1.7 : Fix failing firmware download due to mailbox delays needing to be longer James Smart
2006-08-01 12:20 ` Rolf Eike Beer [this message]
2006-08-01 13:43 ` James Smart
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=200608011420.41752.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Smart@emulex.com \
--cc=linux-scsi@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