From: Johan Hovold <johan@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Johan Hovold" <johan+linaro@kernel.org>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Stanimir Varbanov" <svarbanov@mm-sol.com>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom: Add support for modular builds
Date: Thu, 21 Jul 2022 08:51:35 +0200 [thread overview]
Message-ID: <Ytj3dzQveHhf/0+P@hovoldconsulting.com> (raw)
In-Reply-To: <20220720212053.GA1659584@bhelgaas>
On Wed, Jul 20, 2022 at 04:20:53PM -0500, Bjorn Helgaas wrote:
> On Thu, May 19, 2022 at 11:46:46AM +0200, Johan Hovold wrote:
> > Allow the Qualcomm PCIe controller driver to be built as a module, which
> > is useful for multi-platform kernels as well as during development.
> >
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
>
> This no longer applies on my pci/ctrl/qcom branch:
> 839fbdee4c08 ("dt-bindings: PCI: qcom: Fix reset conditional")
>
> Do you want to refresh it, or should we wait until the next cycle?
I just sent a rebased v2 (the context had changed due to the addition of
the ipq6018 device-id entry):
https://lore.kernel.org/all/20220721064720.10762-1-johan+linaro@kernel.org/
Johan
prev parent reply other threads:[~2022-07-21 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 9:46 Johan Hovold
2022-05-26 20:53 ` Rob Herring
2022-06-23 11:40 ` Johan Hovold
2022-06-23 15:52 ` Bjorn Helgaas
2022-06-27 7:31 ` Johan Hovold
2022-07-14 12:19 ` Stanimir Varbanov
2022-07-14 13:05 ` Dmitry Baryshkov
2022-07-15 16:56 ` Bjorn Helgaas
2022-07-18 7:43 ` Stanimir Varbanov
2022-07-14 13:10 ` Johan Hovold
2022-07-20 16:27 ` Manivannan Sadhasivam
2022-07-20 21:20 ` Bjorn Helgaas
2022-07-21 6:51 ` Johan Hovold [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=Ytj3dzQveHhf/0+P@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=helgaas@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=svarbanov@mm-sol.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
all inboxes | Powered by JetHome®