From: Alexander Gordeev <agordeev@redhat.com>
To: James Smart <james.smart@Emulex.Com>
Cc: linux-scsi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/22] lpfc: Use pci_enable_msix_range()
Date: Sun, 23 Feb 2014 20:45:49 +0100 [thread overview]
Message-ID: <20140223194548.GA16635@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <a34533b1-77d9-45bc-ad66-aab336972b95@CMEXHTCAS2.ad.emulex.com>
On Thu, Feb 20, 2014 at 11:47:02AM -0500, James Smart wrote:
> Alexander,
>
> I've reworked this patch to layer on top of our rev 8.3.45 patches
> that were just posted to linux-scsi. There were some conflicts due to
> new additions. Additionally, there were two other uses of pci_enable_msiXXX
> that needed to be addressed. The changes in this patch also address the
> change requested by:
> "[PATCH 11/22] lpfc: Remove superfluous call to pci_disable_msix()"
>
> To avoid creating merge conflicts - either by your patches going in then
> scsi git tree trying to merge or by scsi git tree going in and your patches
> trying to merge - I recommend that you eliminate your lpfc patches from the
> kernel and apply the patch below once scsi git with the updated lpfc driver
> has actually merged.
Hi James,
Thank you for the review and for the updated patch - it is embarrassing
I have not addressed all pci_enable_msix()'s.
I will keep the two patches separate to ease bisecting -
I am going to repost the patches on top of scsi tree.
Cheers!
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2014-02-23 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 16:47 [PATCH 12/22] lpfc: Use pci_enable_msix_range() James Smart
2014-02-23 19:45 ` Alexander Gordeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-04 11:16 [PATCH 00/22] scsi: " Alexander Gordeev
2014-02-04 11:16 ` [PATCH 12/22] lpfc: " Alexander Gordeev
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=20140223194548.GA16635@dhcp-26-207.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=james.smart@Emulex.Com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).