From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753559Ab0CZLWc (ORCPT ); Fri, 26 Mar 2010 07:22:32 -0400 Received: from mgw2.diku.dk ([130.225.96.92]:42923 "EHLO mgw2.diku.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753502Ab0CZLWa (ORCPT ); Fri, 26 Mar 2010 07:22:30 -0400 Date: Fri, 26 Mar 2010 12:22:27 +0100 (CET) From: Julia Lawall To: Peter Zijlstra Cc: Ingo Molnar , tglx , Oleg Nesterov , LKML Subject: Re: set_cpus_allowed_ptr In-Reply-To: <1269597796.12097.133.camel@laptop> Message-ID: References: <1269597796.12097.133.camel@laptop> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 26 Mar 2010, Peter Zijlstra wrote: > Hi, > > Would it make sense to clean up the set_cpus_allowed() vs > set_cpus_allowed_ptr() mess using the semantic patch tool? > > I guess it would be three patches: > 1) converting the current remaining set_cpus_allowed() users into > set_cpus_allowed_ptr(). > 2) remove set_cpus_allowed(). > 3) rename set_cpus_allowed_ptr() to set_cpus_allowed() Perhaps a subtlety is that set_cpus_allowed is creating a new variable, whose address it sends to set_cpus_allowed_ptr? julia