Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Petr Vorel <petr.vorel@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/6] msm8994-huawei-angler and msm8992-lg-bullhead sdhc1 fixes
Date: Mon, 31 Jan 2022 21:00:14 +0000	[thread overview]
Message-ID: <164366281469.9160.11636865721002054288.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220113233358.17972-1-petr.vorel@gmail.com>

Hello:

This series was applied to qcom/linux.git (for-next)
by Bjorn Andersson <bjorn.andersson@linaro.org>:

On Fri, 14 Jan 2022 00:33:52 +0100 you wrote:
> Hi,
> 
> Besides fixing sdhc1 for msm8994-huawei-angler and msm8992-lg-bullhead
> I also rebased and reposted Jean's patches (Makefile didn't apply on
> current for-next) and also rename angler's DTS.
> 
> sdhc1 (i.e. mmc0) is working on both, but there are overclocking
> warnings. I suspected issue similar to using clk_rcg2_ops instead of
> clk_rcg2_floor_ops (i.e. 3f905469c8ce ("clk: qcom: gcc: Use floor ops
> for SDCC clocks") or 148ddaa89d4a ("clk: qcom: gcc-sc7180: Use floor ops
> for the correct sdcc1 clk"), but it looks to be correct for gcc-msm8994.c.
> 
> [...]

Here is the summary with links:
  - [1/6] arm64: dts: qcom: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file
    https://git.kernel.org/qcom/c/3f99518c6f65
  - [2/6] arm64: dts: qcom: msm8992-lg-bullhead: Add support for LG Bullhead rev 1.0
    https://git.kernel.org/qcom/c/cd4bd4704ec8
  - [3/6] arm64: dts: qcom: msm8994: Provide missing "xo_board" and "sleep_clk" to GCC
    (no matching commit)
  - [4/6] arm64: dts: qcom: msm8994-huawei-angler: Add vendor name huawei
    (no matching commit)
  - [5/6] arm64: dts: qcom: msm8994-huawei-angler: Add sdhc{1,2} definitions
    (no matching commit)
  - [6/6] arm64: dts: qcom: msm8992-lg-bullhead: Disable sdhc2
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-01-31 21:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 23:33 [PATCH 0/6] msm8994-huawei-angler and msm8992-lg-bullhead sdhc1 fixes Petr Vorel
2022-01-13 23:33 ` [PATCH 1/6] arm64: dts: qcom: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file Petr Vorel
2022-01-13 23:33 ` [PATCH 2/6] arm64: dts: qcom: msm8992-lg-bullhead: Add support for LG Bullhead rev 1.0 Petr Vorel
2022-01-13 23:33 ` [PATCH 3/6] arm64: dts: qcom: msm8994: Provide missing "xo_board" and "sleep_clk" to GCC Petr Vorel
2022-01-13 23:33 ` [PATCH 4/6] arm64: dts: qcom: msm8994-huawei-angler: Add vendor name huawei Petr Vorel
2022-01-13 23:33 ` [PATCH 5/6] arm64: dts: qcom: msm8994-huawei-angler: Add sdhc{1,2} definitions Petr Vorel
2022-01-13 23:40   ` Petr Vorel
2022-01-14 18:27     ` Konrad Dybcio
2022-01-14 21:16       ` Petr Vorel
2022-01-14 21:19         ` Konrad Dybcio
2022-01-31 22:43   ` Bjorn Andersson
2022-01-31 22:46     ` Petr Vorel
2022-01-13 23:33 ` [PATCH 6/6] arm64: dts: qcom: msm8992-lg-bullhead: Disable sdhc2 Petr Vorel
2022-01-31 21:00 ` patchwork-bot+linux-arm-msm [this message]
2022-02-01  5:19 ` (subset) [PATCH 0/6] msm8994-huawei-angler and msm8992-lg-bullhead sdhc1 fixes 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=164366281469.9160.11636865721002054288.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=petr.vorel@gmail.com \
    /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