From: James Hogan <jhogan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: [GIT PULL] MIPS fixes for 4.17-rc2
Date: Fri, 20 Apr 2018 15:21:46 +0100 [thread overview]
Message-ID: <20180420142145.GA1521@saruman> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
Hi Linus,
Please pull the following MIPS fixes.
Thanks
James
The following changes since commit a5075e6226c42a8e64ea1b862eec7747dc46cb32:
MIPS: BCM47XX: Use standard reset button for Luxul XWR-1750 (2018-04-07 00:10:48 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/mips.git tags/mips_fixes_4.17_1
for you to fetch changes up to b3d7e55c3f886493235bfee08e1e5a4a27cbcce8:
MIPS: uaccess: Add micromips clobbers to bzero invocation (2018-04-18 22:02:29 +0100)
----------------------------------------------------------------
MIPS fixes for 4.17-rc2
Some MIPS fixes for 4.17:
- io: Add barriers to read*() & write*()
- dts: Fix boston PCI bus DTC warnings (4.17)
- memset: Several corner case fixes (one 3.10, others longer)
----------------------------------------------------------------
Matt Redfearn (5):
MIPS: dts: Boston: Fix PCI bus dtc warnings:
MIPS: memset.S: EVA & fault support for small_memset
MIPS: memset.S: Fix return of __clear_user from Lpartial_fixup
MIPS: memset.S: Fix clobber of v1 in last_fixup
MIPS: uaccess: Add micromips clobbers to bzero invocation
Sinan Kaya (2):
MIPS: io: Prevent compiler reordering writeX()
MIPS: io: Add barrier after register read in readX()
arch/mips/boot/dts/img/boston.dts | 6 ++++++
arch/mips/include/asm/io.h | 4 +++-
arch/mips/include/asm/uaccess.h | 11 +++++++++--
arch/mips/lib/memset.S | 11 ++++++++---
4 files changed, 26 insertions(+), 6 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2018-04-20 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180420142145.GA1521@saruman \
--to=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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