mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH 0/5] clk: qcom: Cleanup redundant header includes
Date: Wed, 18 Mar 2026 12:08:39 +0100	[thread overview]
Message-ID: <20260318-clk-qcom-headers-v1-0-d5c6a3b11b67@oss.qualcomm.com> (raw)

Newly introduced drivers keep repeating same patterns from clock
generation scripts...

Best regards,
Krzysztof

---
Krzysztof Kozlowski (5):
      clk: qcom: kaanapali: Cleanup redundant header includes
      clk: qcom: glymur: Cleanup redundant header includes
      clk: qcom: sm8750: Cleanup redundant header includes
      clk: qcom: milos: Cleanup redundant header includes
      clk: qcom: eliza: Cleanup redundant header includes

 drivers/clk/qcom/cambistmclkcc-kaanapali.c | 2 --
 drivers/clk/qcom/camcc-kaanapali.c         | 2 --
 drivers/clk/qcom/dispcc-glymur.c           | 2 --
 drivers/clk/qcom/dispcc-kaanapali.c        | 2 --
 drivers/clk/qcom/dispcc-milos.c            | 4 +---
 drivers/clk/qcom/gcc-eliza.c               | 1 -
 drivers/clk/qcom/gcc-glymur.c              | 1 -
 drivers/clk/qcom/gcc-kaanapali.c           | 1 -
 drivers/clk/qcom/gpucc-glymur.c            | 1 -
 drivers/clk/qcom/gpucc-kaanapali.c         | 1 -
 drivers/clk/qcom/gxclkctl-kaanapali.c      | 1 -
 drivers/clk/qcom/tcsrcc-eliza.c            | 1 -
 drivers/clk/qcom/tcsrcc-glymur.c           | 1 -
 drivers/clk/qcom/tcsrcc-kaanapali.c        | 1 -
 drivers/clk/qcom/tcsrcc-sm8750.c           | 2 +-
 drivers/clk/qcom/videocc-glymur.c          | 1 -
 drivers/clk/qcom/videocc-sm8750.c          | 1 -
 17 files changed, 2 insertions(+), 23 deletions(-)
---
base-commit: 8e5a478b6d6a5bb0a3d52147862b15e4d826af19
change-id: 20260318-clk-qcom-headers-9b9cbf80a04c

Best regards,
-- 
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>


             reply	other threads:[~2026-03-18 11:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 11:08 Krzysztof Kozlowski [this message]
2026-03-18 11:08 ` [PATCH 1/5] clk: qcom: kaanapali: " Krzysztof Kozlowski
2026-03-18 11:08 ` [PATCH 2/5] clk: qcom: glymur: " Krzysztof Kozlowski
2026-03-18 11:08 ` [PATCH 3/5] clk: qcom: sm8750: " Krzysztof Kozlowski
2026-03-18 11:08 ` [PATCH 4/5] clk: qcom: milos: " Krzysztof Kozlowski
2026-03-18 11:08 ` [PATCH 5/5] clk: qcom: eliza: " Krzysztof Kozlowski
2026-03-18 11:33 ` [PATCH 0/5] clk: qcom: " Konrad Dybcio
2026-03-18 13:48 ` Dmitry Baryshkov
2026-03-19  2:46 ` Bjorn Andersson

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=20260318-clk-qcom-headers-v1-0-d5c6a3b11b67@oss.qualcomm.com \
    --to=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andersson@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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

all inboxes | Powered by JetHome®