From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] mfd: syscon: Remove repetition of the regmap_get_val_endian()
Date: Mon, 24 Oct 2022 10:16:17 +0200 [thread overview]
Message-ID: <424a274f-2095-42b0-6c93-67f7284ba309@leemhuis.info> (raw)
In-Reply-To: <b108978a-77ff-68aa-8c7a-1f6e67629608@leemhuis.info>
On 23.10.22 17:08, Thorsten Leemhuis wrote:
> On 09.10.22 18:39, Guenter Roeck wrote:
>> On Mon, Aug 08, 2022 at 05:08:11PM +0300, Andy Shevchenko wrote:
>>> Since the commit 0dbdb76c0ca8 ("regmap: mmio: Parse endianness
>>> definitions from DT") regmap MMIO parses DT itsef, no need to
>>> repeat this in the caller(s).
>>>
>>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>
>> This patch results in reboot failures for all big endian mips emulations.
>>
>> Sample log:
>>
>> Network interface test passed
>> Boot successful.
>> Rebooting
>> reboot: Restarting system
>> Unable to restart system
>> Reboot failed -- System halted
>>
>> The problem is not seen with little endian mips emulations. Reverting
>> this patch fixes the problem. Bisect log attached.
>>
>> #regzbot introduced: 72a95859728a
>> #regzbot title: Reboot failure on big endian mips systems
>
> #regzbot monitor: https://lore.kernel.org/all/Y0GZwkDwnak2ReTt@zx2c4.com/
#regzbot fixed-by: ca4582c286aa4465
prev parent reply other threads:[~2022-10-24 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 14:08 [PATCH v1 1/1] mfd: syscon: Remove repetition of the regmap_get_val_endian() Andy Shevchenko
2022-09-28 17:17 ` Andy Shevchenko
2022-09-29 18:07 ` Lee Jones
2022-10-23 19:46 ` Jason A. Donenfeld
2022-10-24 7:12 ` Lee Jones
2022-10-09 16:39 ` Guenter Roeck
2022-10-10 6:49 ` Andy Shevchenko
2022-10-23 15:08 ` Thorsten Leemhuis
2022-10-24 8:16 ` Thorsten Leemhuis [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=424a274f-2095-42b0-6c93-67f7284ba309@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).