Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS fixes for v6.1
Date: Sun, 13 Nov 2022 14:35:27 +0100	[thread overview]
Message-ID: <20221113133527.GA3935@alpha.franken.de> (raw)

The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc:

  Linux 6.1-rc4 (2022-11-06 15:07:11 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.1_1

for you to fetch changes up to 648060902aa302331b5d6e4f26d8ee0761d239ab:

  MIPS: pic32: treat port as signed integer (2022-11-11 15:53:58 +0100)

----------------------------------------------------------------
- fix jump label branch range check
- check kmalloc failures in Loongson64 kexec
- fix builds with clang-14
- fix char/int handling in pic32

----------------------------------------------------------------
Jason A. Donenfeld (1):
      MIPS: pic32: treat port as signed integer

Jiaxun Yang (1):
      MIPS: jump_label: Fix compat branch range check

John Thomson (1):
      mips: boot/compressed: use __NO_FORTIFY

Liao Chang (1):
      MIPS: Loongson64: Add WARN_ON on kexec related kmalloc failed

Linus Walleij (1):
      mips: alchemy: gpio: Include the right header

Rongwei Zhang (1):
      MIPS: fix duplicate definitions for exported symbols

 arch/mips/alchemy/common/gpiolib.c        |  2 +-
 arch/mips/boot/compressed/decompress.c    |  1 +
 arch/mips/include/asm/fw/fw.h             |  2 +-
 arch/mips/kernel/jump_label.c             |  2 +-
 arch/mips/kernel/relocate_kernel.S        | 15 +++++----------
 arch/mips/loongson64/reset.c              | 10 ++++++++++
 arch/mips/pic32/pic32mzda/early_console.c | 13 ++++++-------
 arch/mips/pic32/pic32mzda/init.c          |  2 +-
 8 files changed, 26 insertions(+), 21 deletions(-)

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

             reply	other threads:[~2022-11-13 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 13:35 Thomas Bogendoerfer [this message]
2022-11-13 16:01 ` [GIT PULL] MIPS fixes for v6.1 pr-tracker-bot

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=20221113133527.GA3935@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@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