mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roger Lu (陸瑞傑)" <Roger.Lu@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"ribalda@chromium.org" <ribalda@chromium.org>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v2] soc: mediatek: mtk-svs: Enable the IRQ later
Date: Mon, 30 Jan 2023 08:47:14 +0000	[thread overview]
Message-ID: <2dc3962eaec214514565302fd8940c03fa8d0243.camel@mediatek.com> (raw)
In-Reply-To: <36e7ab30-8e59-5fb1-adc8-1a9f0e213b52@gmail.com>

Hi Matthias Sir,

Excuse me for missing this thread. Add Tested-by tag.

On Wed, 2023-01-25 at 20:11 +0100, Matthias Brugger wrote:
> 
> On 21/12/2022 09:56, Matthias Brugger wrote:
> > 
> > 
> > On 20/12/2022 22:35, Ricardo Ribalda wrote:
> > > If the system does not come from reset (like when is booted via
> > > kexec()), the peripheral might triger an IRQ before the data structures
> > > are initialised.
> > > 
> > > Fixes:
> > > 
> > > [    0.227710] Unable to handle kernel NULL pointer dereference at
> > > virtual 
> > > address 0000000000000f08
> > > [    0.227913] Call trace:
> > > [    0.227918]  svs_isr+0x8c/0x538
> > > 
> > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> > 
> > Thanks Ricardo. Roger I'll wait for a Tested-by tag from you to make sure
> > this 
> > time everything is fine.
> > 
> 
> Given the chinese new year holidays I don't expect a Tested-by tag from Roger
> in 
> time. So I just took this one without it.

Tested-by: Roger Lu <roger.lu@mediatek.com>

> 
> Thanks!
> Matthias

      reply	other threads:[~2023-01-30  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 21:35 Ricardo Ribalda
2022-12-21  8:56 ` Matthias Brugger
2023-01-25 19:11   ` Matthias Brugger
2023-01-30  8:47     ` Roger Lu (陸瑞傑) [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=2dc3962eaec214514565302fd8940c03fa8d0243.camel@mediatek.com \
    --to=roger.lu@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=ribalda@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

all inboxes | Powered by JetHome®