From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"arc-linux-dev@synopsys.com" <arc-linux-dev@synopsys.com>
Subject: Re: ARC patches for stable 3.10
Date: Wed, 7 May 2014 10:18:10 +0530 [thread overview]
Message-ID: <5369BB0A.9000503@synopsys.com> (raw)
In-Reply-To: <20140505120835.GB5869@hercules>
Hi Luis,
On Monday 05 May 2014 05:38 PM, Luis Henriques wrote:
> On Wed, Apr 30, 2014 at 09:53:05AM +0000, Vineet Gupta wrote:
>> Hi,
>>
>> Please apply the following mainline commits to stable 3.10 as prerequisites for a
>> patch for 3.15/stable which will follow to Linus right after.
>>
>> 147aece29b15051173eb1e767018135361cdba89 (went in 3.11-rc1)
>> "ARC: Entry Handler tweaks: Simplify branch for in-kernel preemption"
>>
>> fce16bc35ae4a45634f3dc348d8d297a25c277cf (went in 3.12-rc1)
>> "ARC: Entry Handler tweaks: Optimize away redundant IRQ_DISABLE_SAVE"
>>
>> Thx,
>> -Vineet
>> --
>> To unsubscribe from this list: send the line "unsubscribe stable" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Thank you, I'll queue the 2nd patch for the 3.11 kernel (the 1st one
> is already applied).
>
> Cheers,
> --
> Luís
Thanks for this. FWIW, above patch(es) were just a prerequisite for cleanly
applying below to 3.1x
8aa9e85adac6 ARC: !PREEMPT: Ensure Return to kernel mode is IRQ safe
Thx,
-Vineet
next prev parent reply other threads:[~2014-05-07 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 9:53 ARC patches for stable 3.10 Vineet Gupta
2014-05-05 12:08 ` Luis Henriques
2014-05-07 4:48 ` Vineet Gupta [this message]
2014-05-07 9:03 ` Luis Henriques
2014-05-06 22:44 ` 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=5369BB0A.9000503@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=arc-linux-dev@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--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