From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Alexander Motin <mav@ixsystems.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
Nick Wolff <nwolff@ixsystems.com>,
Bjorn Helgaas <bjorn@helgaas.com>,
linux-pci@vger.kernel.org
Subject: Re: pci_bus_distribute_available_resources() is wrong?
Date: Tue, 13 Dec 2022 16:48:21 +0200 [thread overview]
Message-ID: <Y5iQtaNgr0nMWjAI@black.fi.intel.com> (raw)
In-Reply-To: <35208ffe-0aee-b055-0ed7-99b6414af6da@ixsystems.com>
Hi,
On Tue, Dec 13, 2022 at 09:11:12AM -0500, Alexander Motin wrote:
> > I'm also more than happy to test any patches regarding this if someone
> > else wants to work on it ;-)
>
> I was kind of ready to dive in, I hate hacks and tunables to workaround
> bugs. But as I have told, I see this code first time, so my solutions may
> appear not right. But I'll help as I can, if needed.
That's good to hear :) Okay feel free to use any of my previous patches
as base if needed. I can test the Thunderbolt/USB4 and the QEMU PCI/PCIe
topologies so please keep me in the loop when submitting.
next prev parent reply other threads:[~2022-12-13 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ec11223-edb3-5f5c-62cd-3532d92de0a4@ixsystems.com>
[not found] ` <CAErSpo7WrAg5D4xyv0SycoDc1etSspU_TL6XMAK4STYrXDrGNQ@mail.gmail.com>
2022-12-12 21:10 ` pci_bus_distribute_available_resources() is wrong? Alexander Motin
2022-12-13 5:49 ` Mika Westerberg
2022-12-13 14:11 ` Alexander Motin
2022-12-13 14:48 ` Mika Westerberg [this message]
2022-12-13 15:00 ` Alexander Motin
2022-12-13 15:10 ` Mika Westerberg
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=Y5iQtaNgr0nMWjAI@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=linux-pci@vger.kernel.org \
--cc=mav@ixsystems.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=nwolff@ixsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox