archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <>
To: Benjamin Herrenschmidt <>
Cc: Gavin Shan <>,
Subject: Re: [PATCH V9 0/5] Minimal alignment for p2p bars
Date: Mon, 10 Sep 2012 16:42:49 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1347061864.2385.59.camel@pasglop>

On Fri, Sep 7, 2012 at 5:51 PM, Benjamin Herrenschmidt
<> wrote:
> On Fri, 2012-09-07 at 15:49 -0700, Bjorn Helgaas wrote:
>> Assuming they pass Fengguang's build/smoke test, I'll merge that to my
>> "next" branch soon.  Thanks!
> Thanks !
> Any chance you can poke me when you do so ? At that point I'll include
> them as well along with the rest of the stuff that depends on them.

I merged these to my "next" branch and pushed it.  Are you sure you
want to pull that as opposed to just using the
pci/gavin-window-alignment branch?  Both "next" and
"pci/gavin-window-alignment" have identical commits, but
"pci/gavin-window-alignment" is less likely to be rebased.


  reply	other threads:[~2012-09-10 22:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07  5:00 [PATCH V9 0/5] Minimal alignment for p2p bars Gavin Shan
2012-09-07  5:00 ` [PATCH 1/5] pci: weak function returns alignment Gavin Shan
2012-09-07  5:00 ` [PATCH 2/5] pci: resource assignment based on p2p alignment Gavin Shan
2012-09-07  5:00 ` [PATCH 3/5] pci: refactor function pbus_size_mem Gavin Shan
2012-09-07  5:00 ` [PATCH 4/5] ppc/pci: override pcibios_window_alignment Gavin Shan
2012-09-07  5:00 ` [PATCH 5/5] ppc/pnv: I/O and memory alignment for p2p bridges Gavin Shan
2012-09-07 22:49 ` [PATCH V9 0/5] Minimal alignment for p2p bars Bjorn Helgaas
2012-09-07 23:51   ` Benjamin Herrenschmidt
2012-09-10 22:42     ` Bjorn Helgaas [this message]
2012-09-10 23:33       ` Benjamin Herrenschmidt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).