linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paulburton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: [GIT PULL] MIPS fixes
Date: Sat, 26 Oct 2019 15:14:03 -0700	[thread overview]
Message-ID: <20191026221403.mfcxqs6yxgkl5ufx@pburton-laptop> (raw)

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

Hi Linus,

Here are a few small MIPS fixes; please pull.

Thanks,
    Paul


The following changes since commit 4f5cafb5cb8471e54afdc9054d973535614f7675:

  Linux 5.4-rc3 (2019-10-13 16:37:36 -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_3

for you to fetch changes up to b42aa3fd5957e4daf4b69129e5ce752a2a53e7d6:

  MIPS: tlbex: Fix build_restore_pagemask KScratch restore (2019-10-23 21:12:49 -0700)

----------------------------------------------------------------
A few MIPS fixes:

- Fix VDSO time-related function behavior for systems where we need to
  fall back to syscalls, but were instead returning bogus results.

- A fix to TLB exception handlers for Cavium Octeon systems where they
  would inadvertently clobber the $1/$at register.

- A build fix for bcm63xx configurations.

- Switch to using my @kernel.org email address.

----------------------------------------------------------------
Jonas Gorski (1):
      MIPS: bmips: mark exception vectors as char arrays

Paul Burton (2):
      MAINTAINERS: Use @kernel.org address for Paul Burton
      MIPS: tlbex: Fix build_restore_pagemask KScratch restore

Vincenzo Frascino (1):
      mips: vdso: Fix __arch_get_hw_counter()

 .mailmap                                  |  3 ++-
 MAINTAINERS                               | 10 +++++-----
 arch/mips/bcm63xx/prom.c                  |  2 +-
 arch/mips/include/asm/bmips.h             | 10 +++++-----
 arch/mips/include/asm/vdso/gettimeofday.h |  4 +++-
 arch/mips/kernel/smp-bmips.c              |  8 ++++----
 arch/mips/mm/tlbex.c                      | 23 +++++++++++++++--------
 7 files changed, 35 insertions(+), 25 deletions(-)

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

             reply	other threads:[~2019-10-26 22:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 22:14 Paul Burton [this message]
2019-10-26 23:50 ` [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-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-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=20191026221403.mfcxqs6yxgkl5ufx@pburton-laptop \
    --to=paulburton@kernel.org \
    --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).