From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753325AbbKWPD3 (ORCPT ); Mon, 23 Nov 2015 10:03:29 -0500 Received: from mga14.intel.com ([192.55.52.115]:29271 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751833AbbKWPD1 (ORCPT ); Mon, 23 Nov 2015 10:03:27 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,337,1444719600"; d="scan'208";a="827185200" Date: Mon, 23 Nov 2015 23:03:03 +0800 From: Fengguang Wu To: Sebastian Andrzej Siewior Cc: Steven Rostedt , 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 Message-ID: <20151123150303.GA26066@wfg-t540p.sh.intel.com> References: <1448263178-28397-1-git-send-email-jianchuan.wang@windriver.com> <201511231529.iE0YvIjj%fengguang.wu@intel.com> <20151123084325.4f0b4d62@gandalf.local.home> <20151123141408.GA24611@wfg-t540p.sh.intel.com> <5653241F.4070704@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5653241F.4070704@linutronix.de> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 23, 2015 at 03:35:11PM +0100, Sebastian Andrzej Siewior wrote: > 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! Yes, a stable branch name would be better than "linux-4.1.y-rt" that's like to become stable over time. Thanks, Fengguang