From: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@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 15:48:13 +0530 [thread overview]
Message-ID: <d27d1c7b-72c8-4295-b308-52541348d1ea@oss.qualcomm.com> (raw)
In-Reply-To: <7d78ea3c-3de3-4f90-8964-18a962218fca@oss.qualcomm.com>
> 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.
Sure konrad, what I am more afraid here is that patch was in ready to
accept state but somehow got *missed/skipped* to pull in maintainer tree.
I think i was well before that timeline but still couldn't have this
patch in(for v7.3). Not sure if something to change at my end.
Can we atleast pull in for v7.4 now?
--
Regards
Kuldeep
next prev parent reply other threads:[~2026-08-24 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 7:11 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-29 14:16 ` Konrad Dybcio
2026-07-07 7:11 ` [PATCH v9 2/2] arm64: dts: qcom: monaco: " Kuldeep Singh
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
2026-08-24 10:18 ` Kuldeep Singh [this message]
2026-09-16 9:08 ` 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=d27d1c7b-72c8-4295-b308-52541348d1ea@oss.qualcomm.com \
--to=kuldeep.singh@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--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
all inboxes | Powered by JetHome®