public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: bhelgaas@google.com
Cc: Punit Agrawal <punit.agrawal@arm.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	will.deacon@arm.com, x86@kernel.org,
	linux-arm-kernel@lists.infradead.org, lorenzo.pieralisi@arm.com
Subject: [PATCH 0/2] Drop node-local allocation during host controller initialisation
Date: Tue, 28 Aug 2018 16:05:11 +0100	[thread overview]
Message-ID: <20180828150513.32458-1-punit.agrawal@arm.com> (raw)

Hi Bjorn,

As discussed before[0], here are a couple of patches to drop
node-local allocations during host contoller initialisation. This set
covers both arm64 and x86.

I'm posting early to give the patches time on the list as well in next
in case there are issues we've missed.

The patches are based on v4.19-rc1 and has been boot tested on arm64
and compile tested on x86.

Thanks,
Punit

[0] https://www.spinics.net/lists/arm-kernel/msg669746.html

Punit Agrawal (2):
  arm64: PCI: Remove node-local allocations when initialising host
    controller
  x86/PCI: Remove node-local allocation when initialising host
    controller

 arch/arm64/kernel/pci.c | 5 ++---
 arch/x86/pci/acpi.c     | 2 +-
 2 files changed, 3 insertions(+), 4 deletions(-)

-- 
2.18.0


             reply	other threads:[~2018-08-28 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 15:05 Punit Agrawal [this message]
2018-08-28 15:05 ` [PATCH 1/2] arm64: PCI: Remove node-local allocations when initialising host controller Punit Agrawal
2018-08-28 16:45   ` Will Deacon
2018-08-28 15:05 ` [PATCH 2/2] x86/PCI: Remove node-local allocation " Punit Agrawal
2018-09-04 13:24 ` [PATCH 0/2] Drop node-local allocation during host controller initialisation Bjorn Helgaas

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=20180828150513.32458-1-punit.agrawal@arm.com \
    --to=punit.agrawal@arm.com \
    --cc=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=will.deacon@arm.com \
    --cc=x86@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