From: Bjorn Andersson <andersson@kernel.org>
To: quic_bjorande@quicinc.com, quic_clew@quicinc.com,
mathieu.poirier@linaro.org,
Sudeepgoud Patil <quic_sudeepgo@quicinc.com>
Cc: linux-kernel@vger.kernel.org, quic_deesin@quicinc.com,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: (subset) [PATCH V3 0/2] Use of devname for interrupt descriptions and tracepoint support for smp2p
Date: Tue, 2 Jul 2024 22:37:34 -0500 [thread overview]
Message-ID: <171997785365.348959.8013084242190824614.b4-ty@kernel.org> (raw)
In-Reply-To: <20240627104831.4176799-1-quic_sudeepgo@quicinc.com>
On Thu, 27 Jun 2024 16:18:29 +0530, Sudeepgoud Patil wrote:
> This commit enhances the smp2p driver by adding support for using the device
> name in interrupt descriptions and introducing tracepoint functionality.
> These improvements facilitate more effective debugging of smp2p-related issues.
>
> The devname patch, along with the callback to print the irq chip name as the
> device name and the removal of the ‘smp2p’ string from the irq request,
> results in a unique interrupt description.
>
> [...]
Applied, thanks!
[1/2] soc: qcom: smp2p: Use devname for interrupt descriptions
commit: e49380c155940cb47e291a4b3fcb7fdffee6aa4d
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-07-03 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:48 [PATCH V3 0/2] Use of devname for interrupt descriptions and tracepoint support for smp2p Sudeepgoud Patil
2024-06-27 10:48 ` [PATCH V3 1/2] soc: qcom: smp2p: Use devname for interrupt descriptions Sudeepgoud Patil
2024-06-29 13:03 ` Konrad Dybcio
2024-07-02 6:39 ` Sudeep Patil
2024-07-02 7:59 ` Dmitry Baryshkov
2024-06-27 10:48 ` [PATCH V3 2/2] soc: qcom: smp2p: Introduce tracepoint support Sudeepgoud Patil
2024-06-28 9:22 ` Deepak Kumar Singh
2024-06-28 17:36 ` kernel test robot
2024-07-02 8:03 ` Dmitry Baryshkov
2024-07-03 3:37 ` Bjorn Andersson [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=171997785365.348959.8013084242190824614.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=quic_sudeepgo@quicinc.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