From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
James Smart <james.smart@avagotech.com>,
Dick Kennedy <dick.kennedy@avagotech.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/5] scsi: Use pci_(request|release)_mem_regions
Date: Wed, 1 Jun 2016 00:59:29 -0700 [thread overview]
Message-ID: <20160601075929.GC11923@infradead.org> (raw)
In-Reply-To: <1123377cf09b08091957c7d1f58be1601dbfb50c.1464694724.git.jthumshirn@suse.de>
On Tue, May 31, 2016 at 02:05:11PM +0200, Johannes Thumshirn wrote:
> Now that we do have pci_request_mem_regions() and pci_release_mem_regions() at
> hand, use it in the lpfc driver.
This should read lpfc instead of scsi in the subject line.
Also the request side of the patch seems to be missing.
next prev parent reply other threads:[~2016-06-01 7:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 12:05 [PATCH 0/5] Introduce pci_(request|release)_(mem|io)_regions Johannes Thumshirn
2016-05-31 12:05 ` [Intel-wired-lan] " Johannes Thumshirn
2016-05-31 12:05 ` Johannes Thumshirn
2016-05-31 12:05 ` [PATCH 1/5] PCI: Add helpers to request/release memory and I/O regions Johannes Thumshirn
2016-06-01 7:57 ` Christoph Hellwig
2016-05-31 12:05 ` [PATCH 2/5] NVMe: Use pci_(request|release)_mem_regions Johannes Thumshirn
2016-05-31 12:05 ` Johannes Thumshirn
2016-06-01 7:58 ` Christoph Hellwig
2016-06-01 7:58 ` Christoph Hellwig
2016-05-31 12:05 ` [PATCH 3/5] scsi: " Johannes Thumshirn
2016-06-01 7:59 ` Christoph Hellwig [this message]
2016-06-01 8:04 ` Johannes Thumshirn
2016-05-31 12:05 ` [PATCH 4/5] GenWQE: " Johannes Thumshirn
2016-05-31 12:05 ` [PATCH 5/5] ethernet: " Johannes Thumshirn
2016-05-31 12:05 ` [Intel-wired-lan] " Johannes Thumshirn
2016-06-01 7:59 ` Christoph Hellwig
2016-06-01 7:59 ` [Intel-wired-lan] " Christoph Hellwig
2016-06-01 8:51 ` Johannes Thumshirn
2016-06-01 8:51 ` [Intel-wired-lan] " Johannes Thumshirn
2016-06-01 14:56 ` Jeff Kirsher
2016-06-01 14:56 ` [Intel-wired-lan] " Jeff Kirsher
2016-06-01 15:26 ` Johannes Thumshirn
2016-06-01 15:26 ` [Intel-wired-lan] " Johannes Thumshirn
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=20160601075929.GC11923@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=dick.kennedy@avagotech.com \
--cc=james.smart@avagotech.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.