From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Komal Bajaj <komal.bajaj@oss.qualcomm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: sram: Document qcom,shikra-imem compatible
Date: Sat, 18 Jul 2026 08:47:42 +0200 [thread overview]
Message-ID: <c05c19e4-e960-4df3-a848-ee451cd3169e@kernel.org> (raw)
In-Reply-To: <20260717180238.2dysmrp6wanewgmg@hu-mojha-hyd.qualcomm.com>
On 17/07/2026 20:02, Mukesh Ojha wrote:
> On Thu, Jul 16, 2026 at 10:23:26PM -0500, Bjorn Andersson wrote:
>>
>> On Thu, 30 Apr 2026 18:08:04 +0530, Komal Bajaj wrote:
>>> Add compatible for Shikra SoC IMEM.
>>>
>>>
>>
>> Applied, thanks!
>>
>> [1/1] dt-bindings: sram: Document qcom,shikra-imem compatible
>> commit: 26ead60b1a2722627759dc8c279ed336826bb5e1
>>
>>
>> Please make sure to Cc linux-arm-msm@vger.kernel.org, so changes like this
>> shows up in my inbox.
>
> There is a very high chance it can get missed. Is there a better way, like
> adding sram.yaml to the ARM/QUALCOMM mailing list in the MAINTAINERS file?
Sorry, but no. We discussed this on just a few days ago. Exactly this
case. This should not have been posted separately from DTS, thus problem
does not exist in practice, if developer follows expected approach.
If developer did not intend to merge it through Bjorn, but as usually
through DT then everything was fine, list was correct.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-18 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 12:38 [PATCH] dt-bindings: sram: Document qcom,shikra-imem compatible Komal Bajaj
2026-05-21 12:54 ` Konrad Dybcio
2026-05-26 17:49 ` Komal Bajaj
2026-07-17 3:23 ` Bjorn Andersson
2026-07-17 18:02 ` Mukesh Ojha
2026-07-18 6:47 ` Krzysztof Kozlowski [this message]
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=c05c19e4-e960-4df3-a848-ee451cd3169e@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@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