From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH 0/2] PCI: Drop controller CONFIG_OF dependencies
Date: Thu, 10 Nov 2022 15:03:24 -0600 [thread overview]
Message-ID: <20221110210324.GA671663@bhelgaas> (raw)
In-Reply-To: <20221025191339.667614-1-helgaas@kernel.org>
On Tue, Oct 25, 2022 at 02:13:37PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Drop controller CONFIG_OF dependencies so we can compile-test drivers even
> without CONFIG_OF being enabled. OF provides stub functions when CONFIG_OF
> is not set.
>
> Bjorn Helgaas (2):
> PCI: Drop of_match_ptr() to avoid unused variables
> PCI: Drop controller CONFIG_OF dependencies
>
> drivers/pci/controller/Kconfig | 15 ++-------------
> drivers/pci/controller/cadence/Kconfig | 6 ------
> drivers/pci/controller/dwc/Kconfig | 25 ++++++++++++-------------
> drivers/pci/controller/mobiveil/Kconfig | 1 -
> drivers/pci/controller/pci-ftpci100.c | 2 +-
> drivers/pci/controller/pci-v3-semi.c | 2 +-
> 6 files changed, 16 insertions(+), 35 deletions(-)
I put these on my pci/kbuild branch and propose to merge them at the
end. Lorenzo, let me know if you prefer something else.
prev parent reply other threads:[~2022-11-10 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:13 [PATCH 0/2] PCI: Drop controller CONFIG_OF dependencies Bjorn Helgaas
2022-10-25 19:13 ` [PATCH 1/2] PCI: Drop of_match_ptr() to avoid unused variables Bjorn Helgaas
2022-10-25 19:13 ` [PATCH 2/2] PCI: Drop controller CONFIG_OF dependencies Bjorn Helgaas
2022-11-15 15:56 ` Geert Uytterhoeven
2022-11-15 18:07 ` Bjorn Helgaas
2022-11-15 19:27 ` Geert Uytterhoeven
2022-11-15 19:31 ` Pali Rohár
2022-11-15 20:53 ` Bjorn Helgaas
2022-11-15 21:04 ` Pali Rohár
2022-11-10 21:03 ` Bjorn Helgaas [this message]
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=20221110210324.GA671663@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@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).