linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paul.burton@mips.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] MIPS fixes
Date: Sat, 12 Oct 2019 19:04:14 +0000	[thread overview]
Message-ID: <20191012190412.vaazxi325tjnab2d@pburton-laptop> (raw)

[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]

Hi Linus,

Here are a few MIPS fixes for 5.4; please pull.

Thanks,
    Paul


The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:

  Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git tags/mips_fixes_5.4_2

for you to fetch changes up to 2f2b4fd674cadd8c6b40eb629e140a14db4068fd:

  MIPS: Disable Loongson MMI instructions for kernel build (2019-10-10 11:58:52 -0700)

----------------------------------------------------------------
A few MIPS fixes for 5.4:

- Build fixes for CONFIG_OPTIMIZE_INLINING=y builds in which the
  compiler may choose not to inline __xchg() & __cmpxchg().

- A build fix for Loongson configurations with GCC 9.x.

- Expose some extra HWCAP bits to indicate support for various
  instruction set extensions to userland.

- Fix bad stack access in firmware handling code for old SNI
  RM200/300/400 machines.

----------------------------------------------------------------
Jiaxun Yang (1):
      MIPS: elf_hwcap: Export userspace ASEs

Paul Burton (1):
      MIPS: Disable Loongson MMI instructions for kernel build

Thomas Bogendoerfer (3):
      MIPS: include: Mark __cmpxchg as __always_inline
      MIPS: include: Mark __xchg as __always_inline
      MIPS: fw: sni: Fix out of bounds init of o32 stack

 arch/mips/fw/sni/sniprom.c         |  2 +-
 arch/mips/include/asm/cmpxchg.h    |  9 +++++----
 arch/mips/include/uapi/asm/hwcap.h | 11 +++++++++++
 arch/mips/kernel/cpu-probe.c       | 33 +++++++++++++++++++++++++++++++++
 arch/mips/loongson64/Platform      |  4 ++++
 arch/mips/vdso/Makefile            |  1 +
 6 files changed, 55 insertions(+), 5 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2019-10-12 19:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 19:04 Paul Burton [this message]
2019-10-12 21:40 ` [GIT PULL] MIPS fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-02-25  6:58 Paul Burton
2020-02-25 18:55 ` pr-tracker-bot
2020-01-04 20:07 Paul Burton
2020-01-04 22:55 ` pr-tracker-bot
2019-11-15  5:04 Paul Burton
2019-11-15 17:35 ` pr-tracker-bot
2019-10-26 22:14 Paul Burton
2019-10-26 23:50 ` pr-tracker-bot
2019-10-04 20:05 Paul Burton
2019-10-04 20:40 ` pr-tracker-bot
2019-08-06 19:23 Paul Burton
2019-08-06 21:15 ` pr-tracker-bot
2019-07-06 16:23 Paul Burton
2019-07-06 17:40 ` pr-tracker-bot
2019-06-08  6:40 Paul Burton
2019-06-08 20:20 ` pr-tracker-bot
2019-04-09 23:26 Paul Burton
2019-04-10  2:30 ` pr-tracker-bot
2019-03-18 23:08 Paul Burton
2019-03-19 18:15 ` pr-tracker-bot
2019-01-19 19:18 Paul Burton
2019-01-19 22:35 ` 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=20191012190412.vaazxi325tjnab2d@pburton-laptop \
    --to=paul.burton@mips.com \
    --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;
as well as URLs for NNTP newsgroup(s).