Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Neeraj Soni <neeraj.soni@oss.qualcomm.com>
Subject: Re: [PATCH v9 0/2] Enable sdhc inline crypto engine for kodiak and monaco
Date: Mon, 24 Aug 2026 11:21:52 +0200	[thread overview]
Message-ID: <7d78ea3c-3de3-4f90-8964-18a962218fca@oss.qualcomm.com> (raw)
In-Reply-To: <d4c65f68-900e-4d1d-9b31-350d7a88343f@oss.qualcomm.com>

On 8/24/26 10:43 AM, Kuldeep Singh wrote:
> On 21-07-2026 12:43, Kuldeep Singh wrote:
>> On 07-07-2026 12:41, Kuldeep Singh wrote:
>>> The series is combination of below 2 series sent in past. Since, both
>>> need to be picked together, combine them and send as one series.
>>> - https://lore.kernel.org/lkml/20260608041650.541502-1-neeraj.soni@oss.qualcomm.com/
>>> - https://lore.kernel.org/linux-arm-msm/20260409-ice_emmc_clock_addition-v2-0-90bbcc057361@oss.qualcomm.com/
>>>
>>> Document and wire the SDHCI to ICE relationship on Qualcomm platforms
>>> where ICE is modelled as a dedicated DT node.
>>>
>>> This series:
>>> - adds the qcom,ice phandle to the SDHCI binding and enforces the
>>>   qcom,ice vs embedded-reg modelling rule,
>>> - enables ICE for kodiak and monaco by wiring SDHC to the dedicated ICE
>>>   node,
>>> - adds interface clock and power-domain requirements for the ICE node in
>>>   affected DTS files.
>>
>> Konrad/Bjorn, could you please review and let me know for any comments.
> Thanks Konrad for review.
> Bjorn, can you please help in picking patch for v7.3-rc1.

I'm afraid you're unfamiliar with the release process and have
mismatched expectations. The feature development of 7.3 on
maintainer trees is done already and the RCs will only pull in
fixes to the new code.

After v7.3-rc1 is released (and we expect that to happen next
Sunday), for-next branches will be created atop it and maintainers
will be able to accept patches targetting v7.4

Konrad

  reply	other threads:[~2026-08-24  9:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  7:11 [PATCH v9 0/2] Enable sdhc inline crypto engine for kodiak and monaco Kuldeep Singh
2026-07-07  7:11 ` [PATCH v9 1/2] arm64: dts: qcom: kodiak: enable inline crypto engine for SDHC Kuldeep Singh
2026-07-07  7:55   ` sashiko-bot
2026-07-07  8:41     ` Kuldeep Singh
2026-07-29 14:16   ` Konrad Dybcio
2026-07-07  7:11 ` [PATCH v9 2/2] arm64: dts: qcom: monaco: " Kuldeep Singh
2026-07-07  8:05   ` sashiko-bot
2026-07-29 14:16   ` Konrad Dybcio
2026-07-21  7:13 ` [PATCH v9 0/2] Enable sdhc inline crypto engine for kodiak and monaco Kuldeep Singh
2026-08-24  8:43   ` Kuldeep Singh
2026-08-24  9:21     ` Konrad Dybcio [this message]
2026-08-24 10:18       ` Kuldeep Singh

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=7d78ea3c-3de3-4f90-8964-18a962218fca@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuldeep.singh@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neeraj.soni@oss.qualcomm.com \
    --cc=robh@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