From: James Hogan <james.hogan@imgtec.com>
To: Markos Chandras <Markos.Chandras@imgtec.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Ralf Baechle <ralf@linux-mips.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-mips <linux-mips@linux-mips.org>,
Aurelien Jarno <aurelien@aurel32.net>,
"Markos (GMail)" <markos.chandras@gmail.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: Re: Please add my temporary MIPS fixes branch to linux-next
Date: Tue, 26 Aug 2014 10:51:22 +0100 [thread overview]
Message-ID: <53FC589A.6070700@imgtec.com> (raw)
In-Reply-To: <53FC5729.7060306@imgtec.com>
On 26/08/14 10:45, Markos Chandras wrote:
> On 08/23/2014 09:24 PM, Aaro Koskinen wrote:
>> Hi,
>>
>> On Mon, Aug 11, 2014 at 12:09:36PM +0100, James Hogan wrote:
>>> On 30/07/14 17:00, James Hogan wrote:
>>>> 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.
>>>
>>> I sent you a pull request for these fixes prior to v3.16 but
>>> unfortunately they still missed the release, and only two of the patches
>>> were applied in the main v3.17 MIPS merge.
>>>
>>> What are you intentions for the remaining fixes from Markos & Aaro?
>>
>> Ralf, any comments? I think at least this fix is imporant,
>> because currently users can hang OCTEON systems simply by lauching
>> multiple readers of the proc file:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/jhogan/mips.git/commit/?id=08a9c3c9afcf6e8975fc1c9a97e871e6a039c25a
>>
>> A.
>>
> Hi,
>
> I plan to send GregKH another set of fixes to backport to 3.16, and
> since this patch is now in mainline[1], I will include this one as well.
>
> [1]
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=608308682addfdc7b8e2aee88f0e028331d88e4d
This particular fix is already marked for stable.
The ones I applied that aren't marked for stable (but are now needed in
linux-3.16.y) are:
f85b71ceabb9 MIPS: EVA: Add new EVA header
ca4d24f7954f MIPS: Malta: EVA: Rename 'eva_entry' to 'platform_eva_init'
6521d9a436a6 MIPS: CPS: Initialize EVA before bringing up VPEs from
secondary cores
Cheers
James
next prev parent reply other threads:[~2014-08-26 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:00 Please add my temporary MIPS fixes branch to linux-next James Hogan
2014-07-30 17:06 ` 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 [this message]
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=53FC589A.6070700@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=Markos.Chandras@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox