From: Bjorn Helgaas <helgaas@kernel.org>
To: Stanimir Varbanov <svarbanov@mm-sol.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Johan Hovold" <johan+linaro@kernel.org>,
"Selvam Sathappan Periakaruppan" <quic_speriaka@quicinc.com>,
"Baruch Siach" <baruch.siach@siklu.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Robert Marko" <robimarko@gmail.com>,
"Christian Marangi" <ansuelsmth@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: [PATCH 0/2] PCI: qcom: Minor cleanup
Date: Fri, 22 Jul 2022 10:49:17 -0500 [thread overview]
Message-ID: <20220722154919.1826027-1-helgaas@kernel.org> (raw)
From: Bjorn Helgaas <bhelgaas@google.com>
As far as I can tell, qcom doesn't need <linux/interrupt.h>.
The qcom driver supports many variants (1_0_0, 2_1_0, 2_3_2, 2_3_3, 2_4_0,
etc), and the related code was not in an obvious order, which makes it hard
to navigate.
Bjorn Helgaas (2):
PCI: qcom: Drop unnecessary <linux/interrupt.h> include
PCI: qcom: Sort variants by Qcom IP rev
drivers/pci/controller/dwc/pcie-qcom.c | 733 ++++++++++++-------------
1 file changed, 366 insertions(+), 367 deletions(-)
--
2.25.1
next reply other threads:[~2022-07-22 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 15:49 Bjorn Helgaas [this message]
2022-07-22 15:49 ` [PATCH 1/2] PCI: qcom: Drop unnecessary <linux/interrupt.h> include Bjorn Helgaas
2022-07-26 12:21 ` Johan Hovold
2022-07-27 19:28 ` Bjorn Helgaas
2022-07-22 15:49 ` [PATCH 2/2] PCI: qcom: Sort variants by Qcom IP rev Bjorn Helgaas
2022-07-26 12:45 ` Johan Hovold
2022-07-27 22:02 ` Bjorn Helgaas
2022-07-28 12:26 ` Johan Hovold
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=20220722154919.1826027-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=baruch.siach@siklu.com \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.baryshkov@linaro.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=lpieralisi@kernel.org \
--cc=quic_speriaka@quicinc.com \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).