From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Krishna Chaitanya Chundru <quic_krichai@quicinc.com>,
cros-qcom-dts-watchers@chromium.org,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Stephen Boyd <swboyd@chromium.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_vbadigan@quicinc.com,
quic_ramkri@quicinc.com, quic_nitegupt@quicinc.com,
quic_skananth@quicinc.com, quic_parass@quicinc.com,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc7280: Add additional MSI interrupts
Date: Thu, 4 Jan 2024 09:49:49 +0100 [thread overview]
Message-ID: <f1168212-bc6e-4570-869c-2870d6f248ad@linaro.org> (raw)
In-Reply-To: <07b35821-3b95-ce9b-8a62-7eb8cb7a8ddf@quicinc.com>
On 04/01/2024 09:44, Krishna Chaitanya Chundru wrote:
> Hi All,
>
> Can you please review this.
Please look at the kernel release schedule and how it affects SoC trees.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-04 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231218-additional_msi-v1-1-c872ce861a97@quicinc.com>
2024-01-04 8:44 ` [PATCH] arm64: dts: qcom: sc7280: Add additional MSI interrupts Krishna Chaitanya Chundru
2024-01-04 8:49 ` Krzysztof Kozlowski [this message]
2023-12-18 14:02 Krishna chaitanya chundru
2024-01-27 22:34 ` 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=f1168212-bc6e-4570-869c-2870d6f248ad@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_parass@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_skananth@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).