From: James Smart <James.Smart@Emulex.Com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Mark Haverkamp <markh@osdl.org>, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] lpfc: Timer fix
Date: Wed, 21 Dec 2005 13:45:37 -0500 [thread overview]
Message-ID: <43A9A2D1.6040607@emulex.com> (raw)
In-Reply-To: <1135189555.3533.34.camel@mulgrave>
I would assume it's ok to wait until after 2.6.15.
-- james s
James Bottomley wrote:
> On Wed, 2005-12-21 at 12:39 -0500, James Smart wrote:
>> Agreed.
>
> Is this critical for 2.6.15 or can it wait until after 2.6.15 is
> released?
>
> James
>
>
>
prev parent reply other threads:[~2005-12-21 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 21:16 [PATCH] lpfc: Timer fix Mark Haverkamp
2005-12-21 17:39 ` James Smart
2005-12-21 18:25 ` James Bottomley
2005-12-21 18:45 ` James Smart [this message]
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=43A9A2D1.6040607@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@osdl.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