linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Lee Jones <lee@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] MFD for v6.1
Date: Sat, 8 Oct 2022 09:39:46 -0600	[thread overview]
Message-ID: <Y0GZwkDwnak2ReTt@zx2c4.com> (raw)
In-Reply-To: <Yz6Zi7B2RS16sXhT@google.com>

Hi Lee, Andy,

On Thu, Oct 06, 2022 at 10:02:03AM +0100, Lee Jones wrote:
>    - Remove legacy / unused code; stmpe, intel_soc_pmic_crc, syscon
> Andy Shevchenko (13):
>       mfd: syscon: Remove repetition of the regmap_get_val_endian()
>  drivers/mfd/syscon.c                               |    8 -

72a95859728a ("mfd: syscon: Remove repetition of the
regmap_get_val_endian()") broke reboot on big endian MIPS VMs. Scroll to
the bottom of
https://build.wireguard.com/linux/e8bc52cb8df80c31c73c726ab58ea9746e9ff734/mips.log
to see:

[  243.154570] reboot: Restarting system
[  244.157414] Unable to restart system
[  245.159851] Reboot failed -- System halted

Jason

  parent reply	other threads:[~2022-10-08 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  9:02 [GIT PULL] MFD for v6.1 Lee Jones
2022-10-07 19:20 ` pr-tracker-bot
2022-10-08 15:39 ` Jason A. Donenfeld [this message]
2022-10-08 15:47   ` [PATCH] Revert "mfd: syscon: Remove repetition of the regmap_get_val_endian()" Jason A. Donenfeld
2022-10-08 16:45     ` Linus Torvalds
2022-10-08 19:07       ` Andy Shevchenko
2022-10-10  7:48         ` Lee Jones
2022-10-10 15:25           ` Jason A. Donenfeld
2022-10-11  7:39         ` Lee Jones
2022-10-11  9:44           ` Andy Shevchenko
2022-10-11  9:44     ` Andy Shevchenko
2022-10-18  7:23     ` Lee Jones

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=Y0GZwkDwnak2ReTt@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).