From: Frederic Weisbecker <frederic@kernel.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Christoph Hellwig <hch@lst.de>, Tejun Heo <tj@kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Daniel Wagner <wagi@monom.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <clark.williams@gmail.com>,
Julia Cartwright <julia@ni.com>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [patch 1/1] Kconfig: Introduce CONFIG_PREEMPT_RT
Date: Tue, 16 Jul 2019 22:59:07 +0200 [thread overview]
Message-ID: <20190716205907.GC4000@lenoir> (raw)
In-Reply-To: <e245e8ac-d55d-89c8-424a-432e0481cd2a@redhat.com>
On Tue, Jul 16, 2019 at 10:18:00PM +0200, Daniel Bristot de Oliveira wrote:
> On 16/07/2019 22:10, Clark Williams wrote:
> > Excited to see this Thomas. Now I can start planning to build from a single tree
> > rather than an RT tree off to the side of RHEL :)
> >
> > Acked-by: Clark Williams <williams@redhat.com>
> >
>
> yeah! We (Red Hat) are committed with maintaining and testing the PREEMPT RT
> mainstream in the long term. Including the development of more tests and formal
> verification for it!
AND MY AXE!!! (Suse)
Acked-by: Frederic Weisbecker <frederic@kernel.org>
>
> Acked-by: Daniel Bristot de Oliveira <bristot@redhat.com>
>
> Thanks!
> -- Daniel
next prev parent reply other threads:[~2019-07-16 20:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 15:04 [patch 0/1] Kconfig: Introduce CONFIG_PREEMPT_RT Thomas Gleixner
2019-07-15 15:04 ` [patch 1/1] " Thomas Gleixner
2019-07-15 19:47 ` Lukas Bulwahn
2019-07-16 18:20 ` Paul E. McKenney
2019-07-16 20:07 ` Steven Rostedt
2019-07-16 20:10 ` Clark Williams
2019-07-16 20:18 ` Daniel Bristot de Oliveira
2019-07-16 20:59 ` Frederic Weisbecker [this message]
2019-07-16 22:58 ` Ingo Molnar
2019-07-16 23:34 ` Gratian Crisan
2019-07-17 7:38 ` Peter Zijlstra
2019-07-17 7:57 ` Marc Zyngier
2019-07-17 8:45 ` Daniel Wagner
2019-07-17 20:01 ` [patch V2 " Thomas Gleixner
2019-07-18 14:19 ` [tip:sched/urgent] sched/rt, " tip-bot for Thomas Gleixner
2019-07-18 14:50 ` [patch V2 1/1] " Julia Cartwright
2019-07-18 17:52 ` [tip:sched/urgent] sched/rt, " tip-bot for Thomas Gleixner
2019-07-18 19:23 ` [patch V2 1/1] " Tom Zanussi
2019-07-18 21:16 ` [tip:sched/urgent] sched/rt, " tip-bot for Thomas Gleixner
2019-07-17 23:05 ` [patch 1/1] " Luis Claudio R. Goncalves
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=20190716205907.GC4000@lenoir \
--to=frederic@kernel.org \
--cc=akpm@linuxfoundation.org \
--cc=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=clark.williams@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tom.zanussi@linux.intel.com \
--cc=torvalds@linuxfoundation.org \
--cc=wagi@monom.org \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).