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.8
Date: Sun, 5 Jul 2020 12:40:08 +0200 [thread overview]
Message-ID: <20200705104008.GA5156@alpha.franken.de> (raw)
Hi Linus,
please pull the few MIPS fixes.
Thomas.
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_fixes_5.8_1
for you to fetch changes up to 5868347a192afb99b189d72946ab6a321b6115ac:
MIPS: Do not use smp_processor_id() in preemptible code (2020-07-05 11:43:52 +0200)
----------------------------------------------------------------
A few MIPS fixes:
- fix for missing hazard barrier
- DT fix for ingenic
- DT fix of GPHY names for lantiq
- fix usage of smp_processor_id() while preemption is enabled
----------------------------------------------------------------
Hauke Mehrtens (1):
MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
João H. Spies (1):
MIPS: ingenic: gcw0: Fix HP detection GPIO.
Martin Blumenstingl (1):
MIPS: lantiq: xway: sysctrl: fix the GPHY clock alias names
Xingxing Su (1):
MIPS: Do not use smp_processor_id() in preemptible code
arch/mips/boot/dts/ingenic/gcw0.dts | 2 +-
arch/mips/kernel/traps.c | 9 ++++++---
arch/mips/lantiq/xway/sysctrl.c | 8 ++++----
3 files changed, 11 insertions(+), 8 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-07-05 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 10:40 Thomas Bogendoerfer [this message]
2020-07-05 17:35 ` [GIT PULL] MIPS fixes for v5.8 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=20200705104008.GA5156@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;
as well as URLs for NNTP newsgroup(s).