public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Johan Hovold <johan+linaro@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
Subject: Re: [PATCH 0/3] phy: qcom-qmp-pcie: shorten function prefixes
Date: Tue, 13 Sep 2022 20:23:52 +0530	[thread overview]
Message-ID: <YyCZgHx66V3rhv7u@matsya> (raw)
In-Reply-To: <20220906074550.4383-1-johan+linaro@kernel.org>

On 06-09-22, 09:45, Johan Hovold wrote:
> 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.

Applied, thanks

> 
> Once merged I can do the same conversion of the other four QMP drivers.

Patches welcome!

-- 
~Vinod

  parent reply	other threads:[~2022-09-13 17:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  7:45 [PATCH 0/3] phy: qcom-qmp-pcie: shorten function prefixes Johan Hovold
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 ` Vinod Koul [this message]
2022-09-14  6:11   ` [PATCH 0/3] phy: qcom-qmp-pcie: shorten function prefixes 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=YyCZgHx66V3rhv7u@matsya \
    --to=vkoul@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=johan+linaro@kernel.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 \
    /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