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.17
Date: Thu, 3 Mar 2022 17:48:42 +0100 [thread overview]
Message-ID: <20220303164842.GA12460@alpha.franken.de> (raw)
The following changes since commit d9565bf40da22426d2f660cb31700b6858d1911d:
MIPS: DTS: CI20: fix how ddc power is enabled (2022-02-09 13:58:26 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes-5.17_4
for you to fetch changes up to 5d8965704fe5662e2e4a7e4424a2cbe53e182670:
MIPS: ralink: mt7621: use bitwise NOT instead of logical (2022-03-01 10:08:45 +0100)
----------------------------------------------------------------
- Fix memory detection for MT7621 devices
- Fix setnocoherentio kernel option
- Fix warning when CONFIG_SCHED_CORE is enabled
----------------------------------------------------------------
Alexander Lobakin (1):
MIPS: smp: fill in sibling and core maps earlier
Chuanhong Guo (1):
MIPS: ralink: mt7621: do memory detection on KSEG1
Ilya Lipnitskiy (1):
MIPS: ralink: mt7621: use bitwise NOT instead of logical
Randy Dunlap (1):
mips: setup: fix setnocoherentio() boolean setting
arch/mips/kernel/setup.c | 2 +-
arch/mips/kernel/smp.c | 6 +++---
arch/mips/ralink/mt7621.c | 36 +++++++++++++++++++++++-------------
3 files changed, 27 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:[~2022-03-03 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 16:48 Thomas Bogendoerfer [this message]
2022-03-03 19:18 ` [GIT PULL] MIPS fixes for v5.17 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 10:29 Thomas Bogendoerfer
2022-02-10 14:03 ` pr-tracker-bot
2022-02-03 8:56 Thomas Bogendoerfer
2022-02-03 14:57 ` pr-tracker-bot
2022-01-28 13:33 Thomas Bogendoerfer
2022-01-28 17:36 ` 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=20220303164842.GA12460@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.