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: Tue, 6 Aug 2019 19:23:16 +0000 [thread overview]
Message-ID: <20190806192315.y2faix6zk5igs2ry@pburton-laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
Hi Linus,
Here are a few small MIPS fixes for the 5.3 cycle; please pull.
Thanks,
Paul
The following changes since commit e5793cd1b5fedb39337cfa62251a25030f526e56:
MIPS: fix some more fall through errors in arch/mips (2019-07-16 12:40:16 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git tags/mips_fixes_5.3_1
for you to fetch changes up to 74034a09267c1f48d5ce7ae4c4a317fac7d43418:
MIPS: BCM63XX: Mark expected switch fall-through (2019-08-05 18:25:30 -0700)
----------------------------------------------------------------
A few MIPS fixes for 5.3:
- Various switch fall through annotations to fixup warnings & errors
resulting from -Wimplicit-fallthrough.
- A fix for systems (at least jazz) using an i8253 PIT as clocksource
when it's not suitably configured.
- Set struct cacheinfo's cpu_map_populated field to true, indicating
that we filled in cache info detected from cop0 registers & avoiding
complaints about that info being (intentionally) missing in
devicetree.
----------------------------------------------------------------
Gustavo A. R. Silva (2):
MIPS: OProfile: Mark expected switch fall-throughs
MIPS: BCM63XX: Mark expected switch fall-through
Paul Burton (2):
MIPS: Annotate fall-through in kvm/emulate.c
MIPS: Annotate fall-through in Cavium Octeon code
Thomas Bogendoerfer (1):
MIPS: kernel: only use i8253 clocksource with periodic clockevent
Vladimir Kondratiev (1):
mips: fix cacheinfo
arch/mips/cavium-octeon/octeon-usb.c | 1 +
arch/mips/kernel/cacheinfo.c | 2 ++
arch/mips/kernel/i8253.c | 3 ++-
arch/mips/kvm/emulate.c | 1 +
arch/mips/oprofile/op_model_mipsxx.c | 13 +++++++++++++
arch/mips/pci/ops-bcm63xx.c | 1 +
6 files changed, 20 insertions(+), 1 deletion(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2019-08-06 19:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 19:23 Paul Burton [this message]
2019-08-06 21:15 ` [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-12 19:04 Paul Burton
2019-10-12 21:40 ` pr-tracker-bot
2019-10-04 20:05 Paul Burton
2019-10-04 20:40 ` 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=20190806192315.y2faix6zk5igs2ry@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).