From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751314AbdBFKcB (ORCPT ); Mon, 6 Feb 2017 05:32:01 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:33302 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750949AbdBFKcA (ORCPT ); Mon, 6 Feb 2017 05:32:00 -0500 Date: Mon, 6 Feb 2017 11:31:56 +0100 From: Ingo Molnar To: Mike Galbraith Cc: Ingo Molnar , Thomas Gleixner , Sebastian Andrzej Siewior , LKML , Peter Zijlstra Subject: Re: tip: demise of tsk_cpus_allowed() and tsk_nr_cpus_allowed() Message-ID: <20170206103156.GA18908@gmail.com> References: <1486355037.10462.17.camel@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1486355037.10462.17.camel@gmx.de> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Mike Galbraith wrote: > Hi Ingo, > > Doing my ~daily tip merge of -rt, I couldn't help noticing $subject, as > they grow more functionality in -rt, which is allegedly slowly but > surely headed toward merge. I don't suppose they could be left intact? > I can easily restore them in my local tree, but it seems a bit of a > shame to whack these integration friendly bits. Oh, I missed that. How is tsk_cpus_allowed() wrapped in -rt right now? Thanks, Ingo