From: Sumit Garg <sumit.garg@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Casey Connolly <casey.connolly@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
u-boot-qcom@groups.io, u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] Fix variable name of msm_clk_data in two drivers
Date: Wed, 11 Jun 2025 17:45:28 +0530 [thread overview]
Message-ID: <aElzYGfIOgtsF2Q8@sumit-X1> (raw)
In-Reply-To: <20250611-qcom-clk-variable-names-v1-0-37615b74daad@fairphone.com>
On Wed, Jun 11, 2025 at 02:08:43PM +0200, Luca Weiss wrote:
> Just some fixes with no functional change.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> Luca Weiss (2):
> clk/qcom: sc7280: Fix variable name of msm_clk_data
> clk/qcom: sm8250: Fix variable name of msm_clk_data
Nice catch!
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
>
> drivers/clk/qcom/clock-sc7280.c | 4 ++--
> drivers/clk/qcom/clock-sm8250.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
> ---
> base-commit: d7c449c3d83a986d61e38d1762433c0607caf5c5
> change-id: 20250611-qcom-clk-variable-names-0cb615817b3e
>
> Best regards,
> --
> Luca Weiss <luca.weiss@fairphone.com>
>
next prev parent reply other threads:[~2025-06-11 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 12:08 [PATCH 0/2] Fix variable name of msm_clk_data in two drivers Luca Weiss
2025-06-11 12:08 ` [PATCH 1/2] clk/qcom: sc7280: Fix variable name of msm_clk_data Luca Weiss
2025-06-11 12:08 ` [PATCH 2/2] clk/qcom: sm8250: " Luca Weiss
2025-06-12 15:49 ` Alexey Minnekhanov
2025-06-13 6:45 ` Luca Weiss
2025-06-13 16:55 ` Casey Connolly
2025-06-17 8:27 ` Luca Weiss
2025-06-18 11:11 ` Luca Weiss
2025-06-18 18:01 ` Casey Connolly
2025-06-11 12:15 ` Sumit Garg [this message]
2025-06-12 10:42 ` [PATCH 0/2] Fix variable name of msm_clk_data in two drivers Casey Connolly
2025-06-23 23:49 ` Casey Connolly
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=aElzYGfIOgtsF2Q8@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=luca.weiss@fairphone.com \
--cc=lukma@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.