From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Tobias Dahms <dahms.tobias@web.de>,
Sean Wang <sean.wang@mediatek.com>,
angelogioacchino.delregno@collabora.com
Cc: stable@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
linux-leds@vger.kernel.org, linux-wireless@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: kernel error at led trigger "phy0tpt"
Date: Sun, 26 Mar 2023 20:23:53 +0700 [thread overview]
Message-ID: <d14fb08c-70e3-4cc7-caf9-87e73eab9194@gmail.com> (raw)
In-Reply-To: <fcecf6fc-bf18-73a0-9fc1-6850e183323a@web.de>
On 3/26/23 02:20, Tobias Dahms wrote:
> Hello,
>
> the bisection gives following result:
> --------------------------------------------------------------------
> 18c7deca2b812537aa4d928900e208710f1300aa is the first bad commit
> commit 18c7deca2b812537aa4d928900e208710f1300aa
> Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Date: Tue May 17 12:47:08 2022 +0200
>
> soc: mediatek: pwrap: Use readx_poll_timeout() instead of custom
> function
>
> Function pwrap_wait_for_state() is a function that polls an address
> through a helper function, but this is the very same operation that
> the readx_poll_timeout macro means to do.
> Convert all instances of calling pwrap_wait_for_state() to instead
> use the read_poll_timeout macro.
>
> Signed-off-by: AngeloGioacchino Del Regno
> <angelogioacchino.delregno@collabora.com>
> Reviewed-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> Tested-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> Link:
> https://lore.kernel.org/r/20220517104712.24579-2-angelogioacchino.delregno@collabora.com
> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>
> drivers/soc/mediatek/mtk-pmic-wrap.c | 60
> ++++++++++++++++++++----------------
> 1 file changed, 33 insertions(+), 27 deletions(-)
> --------------------------------------------------------------------
>
OK, I'm updating the regression status:
#regzbot introduced: 18c7deca2b8125
And for replying, don't top-post, but rather reply inline with
appropriate context instead; hence I cut the replied context.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-03-26 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 19:44 kernel error at led trigger "phy0tpt" Tobias Dahms
2023-03-21 14:40 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-21 20:22 ` Tobias Dahms
2023-03-22 16:59 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-25 19:20 ` Tobias Dahms
2023-03-26 13:23 ` Bagas Sanjaya [this message]
2023-03-27 8:23 ` AngeloGioacchino Del Regno
2023-04-17 11:25 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 8:17 ` Thorsten Leemhuis
2023-06-05 11:37 ` Thorsten Leemhuis
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=d14fb08c-70e3-4cc7-caf9-87e73eab9194@gmail.com \
--to=bagasdotme@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dahms.tobias@web.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=regressions@lists.linux.dev \
--cc=sean.wang@mediatek.com \
--cc=stable@vger.kernel.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).