linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org, linuxram@us.ibm.com,
	linuxppc-dev@ozlabs.org, bhelgaas@google.com, yinghai@kernel.org
Subject: Re: [PATCH v6 0/7] minimal alignment for p2p bars
Date: Tue, 17 Jul 2012 11:40:25 +0800	[thread overview]
Message-ID: <20120717034025.GC2369@ram-ThinkPad-T61> (raw)
In-Reply-To: <1342491799-30303-1-git-send-email-shangw@linux.vnet.ibm.com>

On Tue, Jul 17, 2012 at 10:23:12AM +0800, Gavin Shan wrote:
> v1 -> v2:
> 	* Shorten the varaible names so that they looks more short.
> 	* Changelog adjustment so that they looks more meaningful.
> 
> v2 -> v3:
> 	* Rebase to 3.5.RC4
> 
> v3 -> v4:
> 	* Merge Yinghai's patches.
> 
> v3 -> v4:
> 	* Split patch for easy review.
> 	* Add function to retrieve the minimal alignment of p2p bridge. 
> 
> v4 -> v5:
> 	* Rebase to 3.5.RC7
> 	* Introduce weak function pcibios_window_alignment() to retrieve
> 	  I/O and memory alignment for P2P bridges.
> 	* Introduce pcibios_window_alignment() for ppc to override the
> 	  PCI function.
> 	* Add ppc_md.pcibios_window_alignment() for specific platform like
> 	  powernv can override ppc's pcibios_window_alignment().
> 
> v5 -> v6:
> 	* Refactor pcibios_window_alignment() so the platform-specific
> 	  implementation needn't return the default alignment according
> 	  to Bjorn's suggestion.
> 	* Simplify pbus_size_mem() according to Bjorn's suggestion: Just
> 	  check the platform required alignment at very end and adjust
> 	  the "min_align" if necessary.
> 
> Lu Yinghai(3):
>   pci: change variable name for find_pci_host_bridge
>   pci: argument pci_bus for find_pci_host_bridge
>   pci: fiddle with conversion of pci and CPU address


Gavin,
	Do you need Yinghai's first 3 patches to implement your
	functionality?

	I dont see those new functions being called from anywhere
	in your patches.

RP

       reply	other threads:[~2012-07-17  3:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1342491799-30303-1-git-send-email-shangw@linux.vnet.ibm.com>
2012-07-17  3:40 ` Ram Pai [this message]
     [not found] ` <1342491799-30303-6-git-send-email-shangw@linux.vnet.ibm.com>
2012-07-17  5:05   ` [PATCH 05/15] pci: resource assignment based on p2p alignment Ram Pai
2012-07-17  5:23     ` Ram Pai
     [not found]       ` <20120717053648.GA18497@shangw>
2012-07-17  5:57         ` Ram Pai
2012-07-17  9:16           ` Benjamin Herrenschmidt
2012-07-17 10:03             ` Ram Pai
2012-07-17 10:38               ` Benjamin Herrenschmidt
2012-07-17 17:14                 ` Bjorn Helgaas
2012-07-18  4:25                   ` Ram Pai
2012-07-18 16:59                     ` Bjorn Helgaas
2012-07-19  7:24                       ` Gavin Shan
     [not found]                   ` <20120718010746.GA4238@shangw>
2012-07-18  5:02                     ` Ram Pai
2012-07-18  4:28                 ` Ram Pai

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=20120717034025.GC2369@ram-ThinkPad-T61 \
    --to=linuxram@us.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=shangw@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 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).