From: Allen Pais <allen.pais@oracle.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 2/4] [V1] sparc64: support forced irq threading
Date: Fri, 20 Dec 2013 20:48:50 +0530 [thread overview]
Message-ID: <52B45FDA.1060204@oracle.com> (raw)
In-Reply-To: <20131220134120.GD10249@linutronix.de>
>
> Please add here some description and forward this upstream. Did this
> series changed since I applied it?
>
I will add the description and send it upstream.
No, nothings changed, only that I re-based the
code to v3.10.24-rt22.
- Allen
next prev parent reply other threads:[~2013-12-20 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 10:29 [PATCH 0/4] PREEMPT_RT support for sparc64 Allen Pais
2013-12-18 10:29 ` [PATCH 1/4] [V1] sparc64: use generic rwsem spinlocks rt Allen Pais
2013-12-18 10:29 ` [PATCH 2/4] [V1] sparc64: support forced irq threading Allen Pais
2013-12-20 13:41 ` Sebastian Andrzej Siewior
2013-12-20 15:18 ` Allen Pais [this message]
2013-12-18 10:29 ` [PATCH 3/4] [V1] sparc64: convert spinloc_t to raw_spinlock_t in mmu_context_t Allen Pais
2013-12-18 10:29 ` [PATCH 4/4] [V1] sparc64: convert ctx_alloc_lock raw_spinlock_t Allen Pais
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=52B45FDA.1060204@oracle.com \
--to=allen.pais@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).