From: Bjorn Helgaas <bhelgaas@google.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] tilegx pci: fix semantic merge conflict with 3527ed81c
Date: Wed, 25 Jul 2012 15:16:43 -0600 [thread overview]
Message-ID: <CAErSpo7P4jCw=gTDR3JabY1F46xWiTF6ru90T86NzuT7Pxu1_A@mail.gmail.com> (raw)
In-Reply-To: <201207251946.q6PJklUm016228@farm-0002.internal.tilera.com>
On Wed, Jul 25, 2012 at 1:40 PM, Chris Metcalf <cmetcalf@tilera.com> wrote:
> Yinghai Lu removed pci_bus.subordinate in pci-next, which meant that
> the tile-next changes to add tilegx PCI support don't build. This
> was expected (seen in linux-next) and this one-line fix is along
> the same lines as commit b918c62e for all other architectures.
>
> Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
You pushed the other tile changes, so I assume you'll do the same with
this one. But let me know if you want me to push it to Linus.
> ---
> arch/tile/kernel/pci_gx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/tile/kernel/pci_gx.c b/arch/tile/kernel/pci_gx.c
> index fa75264..0e213e3 100644
> --- a/arch/tile/kernel/pci_gx.c
> +++ b/arch/tile/kernel/pci_gx.c
> @@ -853,7 +853,7 @@ int __init pcibios_init(void)
> bus = pci_scan_root_bus(NULL, next_busno, controller->ops,
> controller, &resources);
> controller->root_bus = bus;
> - next_busno = bus->subordinate + 1;
> + next_busno = bus->busn_res.end + 1;
>
> }
>
> --
> 1.7.10.3
>
next prev parent reply other threads:[~2012-07-25 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 19:40 [PATCH] tilegx pci: fix semantic merge conflict with 3527ed81c Chris Metcalf
2012-07-25 21:16 ` Bjorn Helgaas [this message]
2012-07-25 22:45 ` Chris Metcalf
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='CAErSpo7P4jCw=gTDR3JabY1F46xWiTF6ru90T86NzuT7Pxu1_A@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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).