From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
Christoph Hellwig <hch@infradead.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.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 5/5] ethernet: Use pci_(request|release)_mem_regions
Date: Wed, 01 Jun 2016 07:56:45 -0700 [thread overview]
Message-ID: <1464793005.2960.3.camel@intel.com> (raw)
In-Reply-To: <20160601085112.ve6k7bzspapjsswf@c203.arch.suse.de>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
On Wed, 2016-06-01 at 10:51 +0200, Johannes Thumshirn wrote:
> On Wed, Jun 01, 2016 at 12:59:56AM -0700, Christoph Hellwig wrote:
> > On Tue, May 31, 2016 at 02:05:13PM +0200, Johannes Thumshirn wrote:
> > > Now that we do have pci_request_mem_regions() and
> pci_release_mem_regions() at
> > > hand, use it in the ethernet drivers.
> >
> > This should probably be one patch per driver.
>
> I though if I do one patch per subsystem it'll be less a hassle for the
> individual maintainers, but if the netdev people want it as split up,
> I'll be
> doing it of cause.
Since almost all the changes are to Intel wired LAN drivers, if you just
split off the atheros change into a separate patch, I would be happy. Then
you could keep just one patch to change all the Intel drivers.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-01 14:56 UTC|newest]
Thread overview: 14+ 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 ` [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-06-01 7:58 ` Christoph Hellwig
2016-05-31 12:05 ` [PATCH 3/5] scsi: " Johannes Thumshirn
2016-06-01 7:59 ` Christoph Hellwig
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-06-01 7:59 ` Christoph Hellwig
2016-06-01 8:51 ` Johannes Thumshirn
2016-06-01 14:56 ` Jeff Kirsher [this message]
2016-06-01 15:26 ` 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=1464793005.2960.3.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=bhelgaas@google.com \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jcliburn@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 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).