From: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Sergey Temerkhanov <s.temerkhanov@gmail.com>,
Sinan Kaya <okaya@codeaurora.org>,
Vadim.Lomovtsev@caviumnetworks.com
Subject: Re: [RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node()
Date: Fri, 12 May 2017 10:18:46 -0700 [thread overview]
Message-ID: <20170512171846.GA21391@localhost.localdomain> (raw)
In-Reply-To: <20170512155040.GA11377@red-moon>
Hi Lorenzo
On Fri, May 12, 2017 at 04:50:40PM +0100, Lorenzo Pieralisi wrote:
> Hi Vadim,
>
> On Fri, May 12, 2017 at 05:44:05AM -0700, Vadim Lomovtsev wrote:
> > Hi Lorenzo,
> >
> > Are there any news related to these patches ?
>
> Not really, I have not received any feedback but I was expecting some
> to make progress here. Have you tested it ?
>
> Please let me know, thanks !
Not yet. Plan to test them after weekend and will get back to you.
>
> Lorenzo
WBR,
Vadim
next prev parent reply other threads:[~2017-05-12 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 10:06 [RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node() Lorenzo Pieralisi
2017-04-26 10:06 ` [RFC/RFT PATCH 2/3] PCI: Add call to set-up NUMA node for struct pci_bus devices Lorenzo Pieralisi
2017-04-26 10:06 ` [RFC/RFT PATCH 3/3] PCI/ACPI: Add ACPI pci_bus_find_numa_node() implementation Lorenzo Pieralisi
2017-05-15 6:13 ` Zhou Wang
2017-05-15 6:13 ` Zhou Wang
2017-05-15 9:17 ` Lorenzo Pieralisi
2017-05-16 3:22 ` Zhou Wang
2017-05-16 3:22 ` Zhou Wang
2017-05-12 12:44 ` [RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node() Vadim Lomovtsev
2017-05-12 15:50 ` Lorenzo Pieralisi
2017-05-12 17:18 ` Vadim Lomovtsev [this message]
2017-05-15 12:57 ` Vadim Lomovtsev
2017-05-15 13:05 ` Lorenzo Pieralisi
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=20170512171846.GA21391@localhost.localdomain \
--to=vadim.lomovtsev@caviumnetworks.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=okaya@codeaurora.org \
--cc=s.temerkhanov@gmail.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.