From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/3] arm64: Mark PMU interrupt IRQF_NO_THREAD
Date: Thu, 14 May 2015 10:19:18 -0700 [thread overview]
Message-ID: <CAMAWPa-G81bUNr5q1a0tpE3LswU2b0KBi4HagL_g0dG-Je0Z5g@mail.gmail.com> (raw)
In-Reply-To: <20150514171056.GH18984@arm.com>
On Thu, May 14, 2015 at 10:10 AM, Will Deacon <will.deacon@arm.com> wrote:
> On Thu, May 14, 2015 at 06:09:23PM +0100, Kevin Hilman wrote:
[...]
>> Which tree is at applied to? I'm not seeing it in -next, and couldn't
>> find it in any branches of the arm64 tree[1]. Sorry to pester, I'm
>> just looking to cherry-pick it from it's proper upstream for testing
>> with a stable/3.18 based kernel.
>
> I don't think Catalin has started putting together our for-next/core branch
> yet, but I'd expect it to appear there when he picks it up.
Cool, thanks.
Kevin
next prev parent reply other threads:[~2015-05-14 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 20:53 [PATCHv2 0/3] Enable PREEMPT_RT_FULL on arm64 Anders Roxell
2015-04-27 20:53 ` [PATCHv2 1/3] arm64: Mark PMU interrupt IRQF_NO_THREAD Anders Roxell
2015-05-14 15:39 ` Sebastian Andrzej Siewior
2015-05-14 15:42 ` Will Deacon
2015-05-14 17:09 ` Kevin Hilman
2015-05-14 17:10 ` Will Deacon
2015-05-14 17:19 ` Kevin Hilman [this message]
2015-05-14 17:24 ` Catalin Marinas
2015-04-27 20:53 ` [PATCHv2 2/3] arm64: Allow forced irq threading Anders Roxell
2015-05-14 15:40 ` Sebastian Andrzej Siewior
2015-04-27 20:53 ` [PATCHv2 3/3] arch/arm64: Enable PREEMPT_RT_FULL Anders Roxell
2015-05-14 15:57 ` Sebastian Andrzej Siewior
2015-05-15 12:08 ` Anders Roxell
2015-05-18 7:18 ` Sebastian Andrzej Siewior
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=CAMAWPa-G81bUNr5q1a0tpE3LswU2b0KBi4HagL_g0dG-Je0Z5g@mail.gmail.com \
--to=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).