From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 5/10] lpfc 8.2.4 : Make lpfc legacy I/O port free
Date: Fri, 11 Jan 2008 11:52:03 -0600 [thread overview]
Message-ID: <1200073924.3286.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1200034380.27954.23.camel@localhost.localdomain>
On Fri, 2008-01-11 at 01:53 -0500, James Smart wrote:
> Make lpfc legacy I/O port free
>
> This is a patch written by Tomohiro Kusumi and submitted to
> linux-scsi:
>
> http://marc.info/?l=linux-scsi&m=118673720712152&w=2
>
> The original patch comment:
>
> This patch makes Emulex lpfc driver legacy I/O port free.
> It has already been acked quite long time ago.
> So I resubmit the patch.
> http://lkml.org/lkml/2006/11/22/28
>
> Current lpfc driver is already using pci_select_bars()
> and pci_enable_device_bars() when the PCI bus has been reset.
> So I think this patch should also be acked.
>
> Tomohiro Kusumi
>
> Signed-off-by: Tomohiro Kusumi <kusumi.tomohiro@jp.fujitsu.com>
> Signed-off-by: James Smart <James.Smart@emulex.com>
You didn't check the diffstat of this one:
lpfc_init.c | 11
lpfc_init.c.orig | 2475 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 2481 insertions(+), 5 deletions(-)
I've manually removed all references to the lpfc_init.c.orig file that
popped into existence with this patch and was deleted with the
subsequent one.
James
next prev parent reply other threads:[~2008-01-11 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 6:53 [PATCH 5/10] lpfc 8.2.4 : Make lpfc legacy I/O port free James Smart
2008-01-11 17:52 ` James Bottomley [this message]
2008-01-14 14:06 ` 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=1200073924.3286.40.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.