From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Fengguang Wu <lkp@intel.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
kbuild-all@01.org, jianchuan.wang@windriver.com,
tglx@linutronix.de, yang.shi@windriver.com
Subject: Re: [kbuild-all] [PATCH] locking_selftest: Save/restore migrate_disable_atomic in locking selftest
Date: Mon, 23 Nov 2015 15:35:11 +0100 [thread overview]
Message-ID: <5653241F.4070704@linutronix.de> (raw)
In-Reply-To: <20151123141408.GA24611@wfg-t540p.sh.intel.com>
On 11/23/2015 03:14 PM, Fengguang Wu wrote:
>> Need to add RT in the subject like "[PATCH RT]". Then perhaps Fengguang
>> can have his tests either ignore these or test against the -rt trees.
>
> Yes sure. Shall I apply RT patches to this tree/branch?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-4.1.y-rt
I'm going to get you your kbot branch where you run bisect tests and
everything and tests the patches against. The problem with this one is
that we will drop it (or leave it stale) once we move to the next major
kernel release.
> Thanks,
> Fengguang
Sebastian
next prev parent reply other threads:[~2015-11-23 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 7:19 [PATCH] locking_selftest: Save/restore migrate_disable_atomic in locking selftest jianchuan.wang
2015-11-23 7:30 ` kbuild test robot
2015-11-23 13:43 ` Steven Rostedt
2015-11-23 14:14 ` [kbuild-all] " Fengguang Wu
2015-11-23 14:17 ` Steven Rostedt
2015-11-23 14:58 ` Fengguang Wu
2015-11-23 14:35 ` Sebastian Andrzej Siewior [this message]
2015-11-23 15:03 ` Fengguang Wu
2015-12-01 17:59 ` Sebastian Andrzej Siewior
2015-12-03 1:53 ` Fengguang Wu
2015-12-11 17:24 ` 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=5653241F.4070704@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jianchuan.wang@windriver.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=yang.shi@windriver.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