From: Will Deacon <will.deacon@arm.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Jingoo Han <jg1.han@samsung.com>,
Jayachandran C <jchandra@broadcom.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
Tanmay Inamdar <tinamdar@apm.com>
Subject: Re: [PATCH] ARM64: PCI: do not enable resources on PROBE_ONLY systems
Date: Thu, 3 Sep 2015 17:42:09 +0100 [thread overview]
Message-ID: <20150903164209.GI877@arm.com> (raw)
In-Reply-To: <20150903163504.GH829@google.com>
Hi Bjorn,
On Thu, Sep 03, 2015 at 05:35:04PM +0100, Bjorn Helgaas wrote:
> On Mon, Aug 31, 2015 at 11:49:20AM -0500, Bjorn Helgaas wrote:
> > OK, if it fixes a problem in my v4.3 pull request, we need to merge
> > it. I missed the connection, probably because I was browsing the
> > v4.2-rc1 tree, which wouldn't have those changes.
> >
> > It's OK with me to merge it via the arm64 tree.
>
> Do you need me to do anything with this? It'd be nice to get it in
> before -rc1. The PCI changes have already been merged, and it'd be
> nice to mention the commit that this fixes.
Nope, it's queued in the arm64 tree. I'm just waiting for a dependent
branch in -tip to get merged before I send my pull request.
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: PCI: do not enable resources on PROBE_ONLY systems
Date: Thu, 3 Sep 2015 17:42:09 +0100 [thread overview]
Message-ID: <20150903164209.GI877@arm.com> (raw)
In-Reply-To: <20150903163504.GH829@google.com>
Hi Bjorn,
On Thu, Sep 03, 2015 at 05:35:04PM +0100, Bjorn Helgaas wrote:
> On Mon, Aug 31, 2015 at 11:49:20AM -0500, Bjorn Helgaas wrote:
> > OK, if it fixes a problem in my v4.3 pull request, we need to merge
> > it. I missed the connection, probably because I was browsing the
> > v4.2-rc1 tree, which wouldn't have those changes.
> >
> > It's OK with me to merge it via the arm64 tree.
>
> Do you need me to do anything with this? It'd be nice to get it in
> before -rc1. The PCI changes have already been merged, and it'd be
> nice to mention the commit that this fixes.
Nope, it's queued in the arm64 tree. I'm just waiting for a dependent
branch in -tip to get merged before I send my pull request.
Cheers,
Will
next prev parent reply other threads:[~2015-09-03 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:13 [PATCH] ARM64: PCI: do not enable resources on PROBE_ONLY systems Lorenzo Pieralisi
2015-07-30 13:13 ` Lorenzo Pieralisi
2015-08-28 21:14 ` Bjorn Helgaas
2015-08-28 21:14 ` Bjorn Helgaas
2015-08-29 12:44 ` Lorenzo Pieralisi
2015-08-29 12:44 ` Lorenzo Pieralisi
2015-08-31 13:28 ` Bjorn Helgaas
2015-08-31 13:28 ` Bjorn Helgaas
2015-08-31 16:33 ` Lorenzo Pieralisi
2015-08-31 16:33 ` Lorenzo Pieralisi
2015-08-31 16:49 ` Bjorn Helgaas
2015-08-31 16:49 ` Bjorn Helgaas
2015-09-03 16:35 ` Bjorn Helgaas
2015-09-03 16:35 ` Bjorn Helgaas
2015-09-03 16:42 ` Will Deacon [this message]
2015-09-03 16:42 ` Will Deacon
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=20150903164209.GI877@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=jchandra@broadcom.com \
--cc=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tinamdar@apm.com \
/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.