All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
	linux-nvme@lists.infradead.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,
	Frank Haverkamp <haver@linux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jay Cliburn <jcliburn@gmail.com>,
	Chris Snook <chris.snook@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH v3 0/6] Introduce pci_(request|release)_(mem|io)_regions
Date: Wed, 08 Jun 2016 16:04:46 -0700	[thread overview]
Message-ID: <1465427086.2736.93.camel@intel.com> (raw)
In-Reply-To: <20160608072854.ivcfvtlgxab2xkmp@c203.arch.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

On Wed, 2016-06-08 at 09:28 +0200, Johannes Thumshirn wrote:
> On Tue, Jun 07, 2016 at 09:44:00AM +0200, Johannes Thumshirn wrote:
> > The first patch in this series introduces the following 4 helper
> functions to
> > the PCI core:
> > 
> > * pci_request_mem_regions()
> > * pci_request_io_regions()
> > * pci_release_mem_regions()
> > * pci_release_io_regions()
> > 
> > which encapsulate the request and release of a PCI device's memory or
> I/O
> > bars.
> > 
> > The subsequent patches convert the drivers, which use the
> > pci_request_selected_regions(pdev, 
> >       pci_select_bars(pdev, IORESOURCE_MEM), name); 
> > and similar pattern to use the new interface.
> > 
> > This was suggested by Christoph Hellwig in
> > http://lists.infradead.org/pipermail/linux-nvme/2016-May/004570.html an
> d
> > tested on kernel v4.6 with NVMe.
> > 
> 
> Btw, as I've seen already Jeff applying the Intel Ethernet patch to his
> tree, I think this should go via the PCI tree as the build dependency is
> the PCI patch.

Bjorn should pick up the entire series, I just applied the Intel patch (and
dependent patches) so we could touch test it.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: jeffrey.t.kirsher@intel.com (Jeff Kirsher)
Subject: [PATCH v3 0/6] Introduce pci_(request|release)_(mem|io)_regions
Date: Wed, 08 Jun 2016 16:04:46 -0700	[thread overview]
Message-ID: <1465427086.2736.93.camel@intel.com> (raw)
In-Reply-To: <20160608072854.ivcfvtlgxab2xkmp@c203.arch.suse.de>

On Wed, 2016-06-08@09:28 +0200, Johannes Thumshirn wrote:
> On Tue, Jun 07, 2016@09:44:00AM +0200, Johannes Thumshirn wrote:
> > The first patch in this series introduces the following 4 helper
> functions to
> > the PCI core:
> >?
> > * pci_request_mem_regions()
> > * pci_request_io_regions()
> > * pci_release_mem_regions()
> > * pci_release_io_regions()
> >?
> > which encapsulate the request and release of a PCI device's memory or
> I/O
> > bars.
> >?
> > The subsequent patches convert the drivers, which use the
> > pci_request_selected_regions(pdev,?
> >???????pci_select_bars(pdev, IORESOURCE_MEM), name);?
> > and similar pattern to use the new interface.
> >?
> > This was suggested by Christoph Hellwig in
> > http://lists.infradead.org/pipermail/linux-nvme/2016-May/004570.html?an
> d
> > tested on kernel v4.6 with NVMe.
> >?
> 
> Btw, as I've seen already Jeff applying the Intel Ethernet patch to his
> tree, I think this should go via the PCI tree as the build dependency is
> the PCI patch.

Bjorn should pick up the entire series, I just applied the Intel patch (and
dependent patches) so we could touch test it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20160608/37d3a717/attachment-0001.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 0/6] Introduce pci_(request|release)_(mem|io)_regions
Date: Wed, 08 Jun 2016 16:04:46 -0700	[thread overview]
Message-ID: <1465427086.2736.93.camel@intel.com> (raw)
In-Reply-To: <20160608072854.ivcfvtlgxab2xkmp@c203.arch.suse.de>

On Wed, 2016-06-08 at 09:28 +0200, Johannes Thumshirn wrote:
> On Tue, Jun 07, 2016 at 09:44:00AM +0200, Johannes Thumshirn wrote:
> > The first patch in this series introduces the following 4 helper
> functions to
> > the PCI core:
> >?
> > * pci_request_mem_regions()
> > * pci_request_io_regions()
> > * pci_release_mem_regions()
> > * pci_release_io_regions()
> >?
> > which encapsulate the request and release of a PCI device's memory or
> I/O
> > bars.
> >?
> > The subsequent patches convert the drivers, which use the
> > pci_request_selected_regions(pdev,?
> >???????pci_select_bars(pdev, IORESOURCE_MEM), name);?
> > and similar pattern to use the new interface.
> >?
> > This was suggested by Christoph Hellwig in
> > http://lists.infradead.org/pipermail/linux-nvme/2016-May/004570.html?an
> d
> > tested on kernel v4.6 with NVMe.
> >?
> 
> Btw, as I've seen already Jeff applying the Intel Ethernet patch to his
> tree, I think this should go via the PCI tree as the build dependency is
> the PCI patch.

Bjorn should pick up the entire series, I just applied the Intel patch (and
dependent patches) so we could touch test it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160608/37d3a717/attachment.asc>

  reply	other threads:[~2016-06-08 23:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  7:44 [PATCH v3 0/6] Introduce pci_(request|release)_(mem|io)_regions Johannes Thumshirn
2016-06-07  7:44 ` [Intel-wired-lan] " Johannes Thumshirn
2016-06-07  7:44 ` Johannes Thumshirn
2016-06-07  7:44 ` [PATCH v3 1/6] PCI: Add helpers to request/release memory and I/O regions Johannes Thumshirn
2016-06-07  7:44 ` [PATCH v3 2/6] NVMe: Use pci_(request|release)_mem_regions Johannes Thumshirn
2016-06-07  7:44   ` Johannes Thumshirn
2016-06-17 11:27   ` Johannes Thumshirn
2016-06-17 11:27     ` Johannes Thumshirn
2016-06-21 22:27     ` Bjorn Helgaas
2016-06-21 22:27       ` Bjorn Helgaas
2016-06-07  7:44 ` [PATCH v3 3/6] lpfc: " Johannes Thumshirn
2016-06-07  7:44 ` [PATCH v3 4/6] GenWQE: " Johannes Thumshirn
2016-06-07  7:44 ` [PATCH v3 5/6] ethernet/intel: " Johannes Thumshirn
2016-06-07  7:44   ` [Intel-wired-lan] " Johannes Thumshirn
2016-06-07  7:44 ` [PATCH v3 6/6] alx: " Johannes Thumshirn
2016-06-07  7:44   ` [Intel-wired-lan] " Johannes Thumshirn
2016-06-07 11:57 ` [PATCH v3 0/6] Introduce pci_(request|release)_(mem|io)_regions Christoph Hellwig
2016-06-07 11:57   ` [Intel-wired-lan] " Christoph Hellwig
2016-06-07 11:57   ` Christoph Hellwig
2016-06-08  7:28 ` Johannes Thumshirn
2016-06-08  7:28   ` [Intel-wired-lan] " Johannes Thumshirn
2016-06-08  7:28   ` Johannes Thumshirn
2016-06-08 23:04   ` Jeff Kirsher [this message]
2016-06-08 23:04     ` [Intel-wired-lan] " Jeff Kirsher
2016-06-08 23:04     ` Jeff Kirsher
2016-06-21 22:28 ` Bjorn Helgaas
2016-06-21 22:28   ` [Intel-wired-lan] " Bjorn Helgaas
2016-06-21 22:28   ` Bjorn Helgaas

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=1465427086.2736.93.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=axboe@fb.com \
    --cc=bhelgaas@google.com \
    --cc=chris.snook@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dick.kennedy@avagotech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haver@linux.vnet.ibm.com \
    --cc=hch@infradead.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=james.smart@avagotech.com \
    --cc=jcliburn@gmail.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jthumshirn@suse.de \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=netdev@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.