All of lore.kernel.org
 help / color / mirror / Atom feed
From: Myron Stowe <myron.stowe@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Gu Zheng <guz.fnst@cn.fujitsu.com>,
	Guo Chao <yan@linux.vnet.ibm.com>,
	linux-pci <linux-pci@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/12] PCI: Double removing fix and allocate 64bit mmio pref
Date: Sun, 1 Dec 2013 10:05:00 -0700	[thread overview]
Message-ID: <CAL-B5D3t=K-m5Y=Vvgv=SnrOLni8rAJC5eW8J1CEBsgafjTemA@mail.gmail.com> (raw)
In-Reply-To: <1385851238-21085-1-git-send-email-yinghai@kernel.org>

Yinghai:

Would you please consider *not* bundling unrelated, or at least
non-dependent, patches together in one series.  As a distrobution
subsystem maintainer, this type of bundling really complicates trying
to identify and isolate key material for bringing in.  It also makes
trying to identify the core content for key fixes, which can occur
many months or years later, significantly more difficult when they
were buried within a series with other unrelated content

Thanks,
 Myron.

On Sat, Nov 30, 2013 at 3:40 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> First 4 are for Gu Zheng <guz.fnst@cn.fujitsu.com> to help double pci
> device removing via sysfs.
> For patch 4, rafael like to have use lock instead of atomic.
>
> Patch 6 are for not enabling realloc auto when 64bit mmio is not there for
> root bus.
>
> Others are about mmio 64 allocation that could help Guo Chao <yan@linux.vnet.ibm.com> on powerpc mmio allocation.
> It will try to assign 64 bit resource above 4g at first.
>
> Patch 1-4 and Patch 5-12 could be appliey seperatedly.
>
> Could be found:
>         git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-3.14
>
> And it is based on current pci/for-linus.
>
> -v2: update after patch that move device_del down to pci_destroy_dev.
>      add "Try best to allocate pref mmio 64bit above 4G"
>
> -v3: refresh and send out after pci_clip_resource() changes,
>      as Bjorn is not happy with attachments.
>
> Yinghai Lu (12):
>   PCI: Use device_release_driver in pci_stop_root_bus
>   PCI: Move back pci_proc_attach_devices calling
>   PCI: Move resources and bus_list releasing to pci_release_dev
>   PCI: Destroy pci dev only once
>   PCI: pcibus address to resource converting take bus instead of dev
>   PCI: Only enable realloc auto when root bus has 64bit mmio
>   PCI: Don't use 4G bus address directly in resource allocation
>   PCI: Try to allocate mem64 above 4G at first
>   PCI: Kill PCIBIOS_MAX_MEM_32
>   PCI: Try best to allocate pref mmio 64bit above 4g
>   PCI: Sort pci root bus resources list
>   intel-gtt: Read 64bit for gmar_bus_addr
>
>  arch/x86/include/asm/pci.h   |   1 -
>  drivers/char/agp/intel-gtt.c |  14 ++--
>  drivers/pci/bus.c            |  74 ++++++++++++++++---
>  drivers/pci/host-bridge.c    |  34 +++++----
>  drivers/pci/probe.c          |  23 +++++-
>  drivers/pci/remove.c         |  31 ++------
>  drivers/pci/setup-bus.c      | 165 ++++++++++++++++++++++++++++++-------------
>  drivers/pci/setup-res.c      |  14 +++-
>  include/linux/pci.h          |  10 +--
>  9 files changed, 257 insertions(+), 109 deletions(-)
>
> --
> 1.8.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-12-01 17:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 22:40 [PATCH v3 00/12] PCI: Double removing fix and allocate 64bit mmio pref Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 01/12] PCI: Use device_release_driver in pci_stop_root_bus Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 02/12] PCI: Move back pci_proc_attach_devices calling Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 03/12] PCI: Move resources and bus_list releasing to pci_release_dev Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 04/12] PCI: Destroy pci dev only once Yinghai Lu
2013-12-01  1:05   ` Rafael J. Wysocki
2013-12-04  2:19     ` Yinghai Lu
2013-12-04 20:03       ` Rafael J. Wysocki
2013-11-30 22:40 ` [PATCH v3 05/12] PCI: pcibus address to resource converting take bus instead of dev Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 06/12] PCI: Only enable realloc auto when root bus has 64bit mmio Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 07/12] PCI: Don't use 4G bus address directly in resource allocation Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 08/12] PCI: Try to allocate mem64 above 4G at first Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 09/12] PCI: Kill PCIBIOS_MAX_MEM_32 Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 10/12] PCI: Try best to allocate pref mmio 64bit above 4g Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 11/12] PCI: Sort pci root bus resources list Yinghai Lu
2013-12-02 23:11   ` Bjorn Helgaas
2013-12-04  2:12     ` Yinghai Lu
2013-11-30 22:40 ` [PATCH v3 12/12] intel-gtt: Read 64bit for gmar_bus_addr Yinghai Lu
2013-12-01 17:05 ` Myron Stowe [this message]
2013-12-04  2:03   ` [PATCH v3 00/12] PCI: Double removing fix and allocate 64bit mmio pref Yinghai Lu

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='CAL-B5D3t=K-m5Y=Vvgv=SnrOLni8rAJC5eW8J1CEBsgafjTemA@mail.gmail.com' \
    --to=myron.stowe@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=yan@linux.vnet.ibm.com \
    --cc=yinghai@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.