From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Mark Brown <broonie@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-mediatek@lists.infradead.org,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [BUG] 6.2-rc1 spi-mt65xx broken on mt7986
Date: Thu, 5 Jan 2023 13:59:56 +0100 [thread overview]
Message-ID: <752823ee-1aec-7536-095d-6a018e1dd909@leemhuis.info> (raw)
In-Reply-To: <CANiDSCunU4dqiDgNr2mz=MxD+wzTu6V2vZWqY+AC4DqQvwVh4w@mail.gmail.com>
On 05.01.23 13:40, Ricardo Ribalda wrote:
>
> I replied on my phone, so the mail came out in html and the list did
> not pick it up, then Frank also answered in html.
>
> I believe we are good with this:
> https://lore.kernel.org/all/Y7WOlkuLaLt1DdY+@sirena.org.uk/
Ohh, that was the same issue? I had missed that (and it's pretty obvious
when I look at it now :-/ ). Sorry for the noise then, but these things
happen when dealing with so many different regressions.
> Thanks for headsup anyway
Many thx for clarifying!
#regzbot fix: spi: mediatek: Enable irq when pdata is ready
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
> On Thu, 5 Jan 2023 at 13:21, Thorsten Leemhuis
> <regressions@leemhuis.info> wrote:
>>
>> [CCing the regression mailing list, as it should be in the loop:
>> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>>
>> On 27.12.22 11:28, Frank Wunderlich wrote:
>>> Hi,
>>>
>>> the following commit breaks SPIM-NOR on mt7986:
>>>
>>> c6f7874687f7 2022-11-28 spi: mediatek: Enable irq when pdata is ready
>>
>> Ricardo, do you have this report on your radar? Just wondering, as it
>> was posted a week ago and didn't even get a single reply afaics. This of
>> course can happen at this time of the year, but I thought a quick status
>> inquiry wouldn't hurt.
>>
>>>> [ 2.145931] pc : mtk_spi_can_dma+0x0/0x34
>>>> [ 2.155212] lr : mtk_spi_interrupt+0x74/0x360
>>>>
>>>> [ 2.091801] mtk-spi 1100a000.spi: spi-mem transfer timeout
>>>> [ 2.097310] spi-nor: probe of spi0.0 failed with error -110
>>>> [ 2.102930] Unable to handle kernel read from unreadable memory at virtual address 0000000000000010
>>>
>>> after reverting the commit, no trace happens and nor is recognized on my board
>>
>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>> --
>> Everything you wanna know about Linux kernel regression tracking:
>> https://linux-regtracking.leemhuis.info/about/#tldr
>> If I did something stupid, please tell me, as explained on that page.
>>
>> #regzbot poke
>
>
>
next prev parent reply other threads:[~2023-01-05 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 10:28 [BUG] 6.2-rc1 spi-mt65xx broken on mt7986 Frank Wunderlich
2022-12-27 14:29 ` [BUG] 6.2-rc1 spi-mt65xx broken on mt7986 #forregzbot Thorsten Leemhuis
2023-01-05 12:21 ` [BUG] 6.2-rc1 spi-mt65xx broken on mt7986 Thorsten Leemhuis
2023-01-05 12:40 ` Ricardo Ribalda
2023-01-05 12:59 ` Thorsten Leemhuis [this message]
2023-01-05 13:34 ` Linux kernel regression tracking (#update)
2023-01-05 14:36 ` Ricardo Ribalda
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=752823ee-1aec-7536-095d-6a018e1dd909@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=regressions@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).