From: James Hogan <james.hogan@imgtec.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Ralf <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
"Markos (GMail)" <markos.chandras@gmail.com>,
Markos <markos.chandras@imgtec.com>,
Paul <paul.burton@imgtec.com>,
Rob Kendrick <rob.kendrick@codethink.co.uk>,
Alex Smith <alex@alex-smith.me.uk>,
"Huacai Chen" <chenhc@lemote.com>
Subject: Please add my temporary MIPS fixes branch to linux-next
Date: Wed, 30 Jul 2014 17:00:29 +0100 [thread overview]
Message-ID: <53D9169D.3020705@imgtec.com> (raw)
Hi Stephen & MIPS people
v3.16 is fast approaching and there are quite a few important MIPS
patches pending. Since Ralf appears to be unavailable at the moment I've
reviewed and applied some of those patches which are least controversial
to a fixes branch with the intention of sending a pull request to Ralf &
Linus so that one of them can hopefully merge it before the release.
Please could the following branch be added to linux-next:
git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/mips.git
branch: mips-fixes
Details of fixes below.
Thanks
James
The current shortlog looks like this:
Aaro Koskinen (1):
MIPS: OCTEON: make get_system_type() thread-safe
Markos Chandras (5):
MIPS: syscall: Fix AUDIT value for O32 processes on MIPS64
MIPS: scall64-o32: Fix indirect syscall detection
MIPS: EVA: Add new EVA header
MIPS: Malta: EVA: Rename 'eva_entry' to 'platform_eva_init'
MIPS: CPS: Initialize EVA before bringing up VPEs from secondary cores
Paul Burton (1):
MIPS: prevent user from setting FCSR cause bits
Rob Kendrick (1):
MIPS: math-emu: cp1emu: Fix typo when returning to register file
If I've missed any other critical fixes for v3.16 please let me know.
I haven't included the patches below, even though they are important, as
I'm less sure about them. Comments welcome.
This one fixes mips32 debian boot, but changes the layout of the
NT_PRSTATUS regset which is accessible through ptrace. I don't believe
this will break anything, but there are other patches pending in the
patchset to fix up the regset stuff properly anyway (as it is already
broken for core dumps) and I don't really want to take the risk without
Ralf's okay.
Alex Smith (1):
MIPS: O32/32-bit: Fix bug which can cause incorrect system call
restarts
This one I'm not confident about, hasn't had any comments on the list,
and has been broken for quite a while anyway, so I haven't risked it.
Huacai Chen (1):
MIPS: tlbex: fix a missing statement for HUGETLB
next reply other threads:[~2014-07-30 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:00 James Hogan [this message]
2014-07-30 17:06 ` Please add my temporary MIPS fixes branch to linux-next David Daney
2014-07-30 18:17 ` Alex Smith
2014-07-31 8:25 ` James Hogan
2014-07-30 23:06 ` Stephen Rothwell
2014-08-11 11:09 ` James Hogan
2014-08-23 20:24 ` Aaro Koskinen
2014-08-26 9:45 ` Markos Chandras
2014-08-26 9:51 ` James Hogan
2014-08-26 9:55 ` Markos Chandras
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=53D9169D.3020705@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=aaro.koskinen@iki.fi \
--cc=alex@alex-smith.me.uk \
--cc=aurelien@aurel32.net \
--cc=chenhc@lemote.com \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@gmail.com \
--cc=markos.chandras@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=rob.kendrick@codethink.co.uk \
--cc=sfr@canb.auug.org.au \
/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.