From: Thomas Gleixner <tglx@linutronix.de>
To: Manish Jaggi <mjaggi@caviumnetworks.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: When would be preempt_rt patchet available for 4.2 kernel
Date: Wed, 9 Sep 2015 16:28:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509091618300.3854@nanos> (raw)
In-Reply-To: <55F0307E.8050501@caviumnetworks.com>
B1;2802;0cOn Wed, 9 Sep 2015, Manish Jaggi wrote:
> I am working on linux 4.2 kernel for our ARM64 platform.
That's lame. I'm working on linux 5.0 kernel for my new arch/zilchcore
platform.
> Can someone please tell when would be the preempt_rt patchset be
> available for 4.2
Once the 5.0 RT support for zilchcore is finished.
Thanks,
tglx
next prev parent reply other threads:[~2015-09-09 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 13:13 When would be preempt_rt patchet available for 4.2 kernel Manish Jaggi
2015-09-09 14:28 ` Thomas Gleixner [this message]
2015-09-09 18:11 ` Albino B Neto
2015-09-09 20:01 ` Ralf Mardorf
2015-09-14 11:28 ` Jaggi, Manish
2015-09-14 11:42 ` Thomas Gleixner
2015-09-14 17:11 ` Daniel Vacek
2015-09-15 1:37 ` Mike Galbraith
2015-09-15 6:49 ` Daniel Vacek
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=alpine.DEB.2.11.1509091618300.3854@nanos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mjaggi@caviumnetworks.com \
/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