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 v5.9
Date: Fri, 25 Sep 2020 20:07:08 +0200 [thread overview]
Message-ID: <20200925180708.GA5280@alpha.franken.de> (raw)
The following changes since commit b959b97860d0fee8c8f6a3e641d3c2ad76eab6be:
MIPS: SNI: Fix spurious interrupts (2020-09-16 22:40:58 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_fixes_5.9_3
for you to fetch changes up to be090fa62080d8501a5651a73cb954721966b125:
MIPS: BCM47XX: Remove the needless check with the 1074K (2020-09-23 14:48:53 +0200)
----------------------------------------------------------------
- fixed FP register access on Loongsoon-3
- added missing 1074 cpu handling
- fixed Loongson2ef build error
----------------------------------------------------------------
Huacai Chen (1):
MIPS: Loongson-3: Fix fp register access if MSA enabled
Jiaxun Yang (1):
MIPS: Loongson2ef: Disable Loongson MMI instructions
Wei Li (2):
MIPS: Add the missing 'CPU_1074K' into __get_cpu_type()
MIPS: BCM47XX: Remove the needless check with the 1074K
arch/mips/bcm47xx/setup.c | 2 +-
arch/mips/include/asm/cpu-type.h | 1 +
arch/mips/loongson2ef/Platform | 4 ++++
arch/mips/loongson64/cop2-ex.c | 24 ++++++++----------------
4 files changed, 14 insertions(+), 17 deletions(-)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2020-09-25 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 18:07 Thomas Bogendoerfer [this message]
2020-09-25 22:27 ` [GIT PULL] MIPS fixes for v5.9 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-09-17 14:47 Thomas Bogendoerfer
2020-09-17 19:01 ` pr-tracker-bot
2020-09-04 12:32 Thomas Bogendoerfer
2020-09-04 20:49 ` 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=20200925180708.GA5280@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