Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Georgi Djakov <djakov@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] interconnect: qcom: constify qcom_icc_desc
Date: Wed, 27 Apr 2022 18:31:32 +0300	[thread overview]
Message-ID: <99491be0-a438-cac7-1441-396aade91ea4@kernel.org> (raw)
In-Reply-To: <6d9ded33-f5fc-6346-51ca-2de8e7a644ec@linaro.org>


On 27.04.22 15:59, Krzysztof Kozlowski wrote:
> On 27/04/2022 14:17, Georgi Djakov wrote:
>> On 22.04.22 18:25, Krzysztof Kozlowski wrote:
>>> On 12/04/2022 12:26, Krzysztof Kozlowski wrote:
>>>> struct qcom_icc_desc is not modified so it can be made const for safety.
>>>>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> ---
>>>>    drivers/interconnect/qcom/msm8916.c |  6 +++---
>>>>    drivers/interconnect/qcom/msm8939.c |  8 ++++----
>>>>    drivers/interconnect/qcom/msm8974.c | 12 ++++++------
>>>>    drivers/interconnect/qcom/qcm2290.c | 12 ++++++------
>>>>    drivers/interconnect/qcom/qcs404.c  |  6 +++---
>>>>    drivers/interconnect/qcom/sc7180.c  | 26 +++++++++++++-------------
>>>>    drivers/interconnect/qcom/sc7280.c  | 24 ++++++++++++------------
>>>>    drivers/interconnect/qcom/sdm660.c  | 12 ++++++------
>>>>    drivers/interconnect/qcom/sm8150.c  | 22 +++++++++++-----------
>>>>    drivers/interconnect/qcom/sm8250.c  | 22 +++++++++++-----------
>>>>    drivers/interconnect/qcom/sm8350.c  | 20 ++++++++++----------
>>>>    drivers/interconnect/qcom/sm8450.c  | 22 +++++++++++-----------
>>>
>>> Hi folks,
>>>
>>> Any comments here?
>>
>> Thanks for the patches! I had actually some of these changes in my local tree
>> for a long time.
> 
> Indeed I see them now in linux-next. Sorry for pinging, I just did not
> get any notification they got applied.

I meant that i did similar changes, that i never sent upstream, so thanks
for doing this. Pings are welcome.

BR,
Georgi

      reply	other threads:[~2022-04-27 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 10:26 [PATCH 1/3] interconnect: qcom: constify qcom_icc_desc Krzysztof Kozlowski
2022-04-12 10:26 ` [PATCH 2/3] interconnect: qcom: constify icc_node pointers Krzysztof Kozlowski
2022-04-12 10:26 ` [PATCH 3/3] interconnect: qcom: constify qcom_icc_bcm pointers Krzysztof Kozlowski
2022-04-22 15:25 ` [PATCH 1/3] interconnect: qcom: constify qcom_icc_desc Krzysztof Kozlowski
2022-04-27 12:17   ` Georgi Djakov
2022-04-27 12:59     ` Krzysztof Kozlowski
2022-04-27 15:31       ` Georgi Djakov [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=99491be0-a438-cac7-1441-396aade91ea4@kernel.org \
    --to=djakov@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.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