From: Johan Hovold <johan+linaro@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/3] phy: qcom-qmp-pcie: shorten function prefixes
Date: Tue, 6 Sep 2022 09:45:47 +0200 [thread overview]
Message-ID: <20220906074550.4383-1-johan+linaro@kernel.org> (raw)
The QMP PHY driver function prefixes have become unnecessarily long
(e.g. after the recent driver split) and hurt readability.
This series shortens the "qcom_qmp_phy_pcie" prefix to "qmp_pcie" (QMP
likely stands for "Qualcomm Multi PHY" or similar anyway) and clean up
the code somewhat.
Once merged I can do the same conversion of the other four QMP drivers.
Johan
Dmitry Baryshkov (1):
phy: qcom-qmp-pcie: drop if (table) conditions
Johan Hovold (2):
phy: qcom-qmp-pcie: shorten function prefixes
phy: qcom-qmp: drop dual-lane comments
drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 1 -
drivers/phy/qualcomm/phy-qcom-qmp-pcie.c | 145 ++++++++++------------
drivers/phy/qualcomm/phy-qcom-qmp-ufs.c | 1 -
drivers/phy/qualcomm/phy-qcom-qmp-usb.c | 1 -
4 files changed, 63 insertions(+), 85 deletions(-)
--
2.35.1
next reply other threads:[~2022-09-06 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 7:45 Johan Hovold [this message]
2022-09-06 7:45 ` [PATCH 1/3] phy: qcom-qmp-pcie: drop if (table) conditions Johan Hovold
2022-09-06 7:45 ` [PATCH 2/3] phy: qcom-qmp-pcie: shorten function prefixes Johan Hovold
2022-09-09 9:16 ` Dmitry Baryshkov
2022-09-06 7:45 ` [PATCH 3/3] phy: qcom-qmp: drop dual-lane comments Johan Hovold
2022-09-09 9:18 ` Dmitry Baryshkov
2022-09-13 14:53 ` [PATCH 0/3] phy: qcom-qmp-pcie: shorten function prefixes Vinod Koul
2022-09-14 6:11 ` 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=20220906074550.4383-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@ti.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=vkoul@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