public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: tglx@linutronix.de, maz@kernel.org, bjorn.andersson@linaro.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm8450: Fix the IRQ trigger type for remoteproc nodes
Date: Tue, 31 May 2022 12:34:05 +0530	[thread overview]
Message-ID: <20220531070405.GA15569@thinkpad> (raw)
In-Reply-To: <04af7d5f-a4d1-3403-c481-1cc2bb13d30f@linaro.org>

On Tue, May 31, 2022 at 01:39:32AM +0300, Dmitry Baryshkov wrote:
> On 30/05/2022 11:08, Manivannan Sadhasivam wrote:
> > The watchdog IRQ trigger type should be EDGE_RISING. So fix all remoteproc
> > nodes.
> > 
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> 
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> 
> BTW: Could you please send the same patches for sm8250/8350 too?
> 

Hmm... I thought I covered them but apparently missed. Fill fix them too.

Thanks,
Mani

> -- 
> With best wishes
> Dmitry

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2022-05-31  7:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  8:08 [PATCH 0/3] Check for IRQ trigger type mismatch in __setup_irq() Manivannan Sadhasivam
2022-05-30  8:08 ` [PATCH 1/3] ARM: dts: qcom: sdx55: Fix the IRQ trigger type for UART Manivannan Sadhasivam
2022-07-03  3:56   ` (subset) " Bjorn Andersson
2022-05-30  8:08 ` [PATCH 2/3] arm64: dts: qcom: sm8450: Fix the IRQ trigger type for remoteproc nodes Manivannan Sadhasivam
2022-05-30 22:39   ` Dmitry Baryshkov
2022-05-31  7:04     ` Manivannan Sadhasivam [this message]
2022-07-03  3:56   ` (subset) " Bjorn Andersson
2022-05-30  8:08 ` [PATCH 3/3] genirq: Check for trigger type mismatch in __setup_irq() Manivannan Sadhasivam
2022-06-06  8:49   ` Marc Zyngier
2022-11-11 10:41     ` Luca Weiss
2023-02-13  8:46       ` Luca Weiss

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=20220531070405.GA15569@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    /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