Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Greg KH <greg@kroah.com>
Cc: <stable@vger.kernel.org>, <linux-mips@linux-mips.org>
Subject: Re: [request for stable inclusion] MIPS fixes for 3.16
Date: Thu, 28 Aug 2014 08:54:49 +0100	[thread overview]
Message-ID: <53FEE049.8030906@imgtec.com> (raw)
In-Reply-To: <20140827212310.GA27456@kroah.com>

On 08/27/2014 10:23 PM, Greg KH wrote:
> On Wed, Aug 27, 2014 at 03:04:51PM +0100, Markos Chandras wrote:
>> Hi Greg,
>>
>> Could you please apply the following patches to the 3.16.X stable kernels?
>>
>> - MIPS: EVA: Add new EVA header
>> (f85b71ceabb9d8d8a9e34b045b5c43ffde3623b3)
>> - MIPS: Malta: EVA: Rename 'eva_entry' to 'platform_eva_init'
>> (ca4d24f7954f3746742ba350c2276ff777f21173)
>> - MIPS: CPS: Initialize EVA before bringing up VPEs from secondary cores
>> (6521d9a436a62e83ce57d6be6e5484e1098c1380)
> 
> That really looks like a new feature, how is this a bugfix / regression
> from previous kernel releases?
> 
> thanks,
> 
> greg k-h
> 
Hi Greg,

The bugfix is the 3rd patch in that list. Without this patch, it is not
possible to boot a CPS kernel when EVA is enabled. The kernel will die
in a horrible way. The other two patches simply make the bugfix fit
better in the existing code. So all three are needed.

Thank you

-- 
markos

WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [request for stable inclusion] MIPS fixes for 3.16
Date: Thu, 28 Aug 2014 08:54:49 +0100	[thread overview]
Message-ID: <53FEE049.8030906@imgtec.com> (raw)
Message-ID: <20140828075449.DsA6lAUNRnhz_eXvK0CwLh1SG0l4Z9gBqOXd3USnCD0@z> (raw)
In-Reply-To: <20140827212310.GA27456@kroah.com>

On 08/27/2014 10:23 PM, Greg KH wrote:
> On Wed, Aug 27, 2014 at 03:04:51PM +0100, Markos Chandras wrote:
>> Hi Greg,
>>
>> Could you please apply the following patches to the 3.16.X stable kernels?
>>
>> - MIPS: EVA: Add new EVA header
>> (f85b71ceabb9d8d8a9e34b045b5c43ffde3623b3)
>> - MIPS: Malta: EVA: Rename 'eva_entry' to 'platform_eva_init'
>> (ca4d24f7954f3746742ba350c2276ff777f21173)
>> - MIPS: CPS: Initialize EVA before bringing up VPEs from secondary cores
>> (6521d9a436a62e83ce57d6be6e5484e1098c1380)
> 
> That really looks like a new feature, how is this a bugfix / regression
> from previous kernel releases?
> 
> thanks,
> 
> greg k-h
> 
Hi Greg,

The bugfix is the 3rd patch in that list. Without this patch, it is not
possible to boot a CPS kernel when EVA is enabled. The kernel will die
in a horrible way. The other two patches simply make the bugfix fit
better in the existing code. So all three are needed.

Thank you

-- 
markos

  reply	other threads:[~2014-08-28  7:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 14:04 [request for stable inclusion] MIPS fixes for 3.16 Markos Chandras
2014-08-27 14:04 ` Markos Chandras
2014-08-27 21:23 ` Greg KH
2014-08-28  7:54   ` Markos Chandras [this message]
2014-08-28  7:54     ` Markos Chandras
2014-09-04 13:52     ` Markos Chandras
2014-09-04 13:52       ` Markos Chandras
2014-09-04 14:09       ` Greg KH

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=53FEE049.8030906@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=greg@kroah.com \
    --cc=linux-mips@linux-mips.org \
    --cc=stable@vger.kernel.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