Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp786984imu; Fri, 25 Jan 2019 10:59:04 -0800 (PST) X-Google-Smtp-Source: ALg8bN7OvhQU9bBztR9w7rCl1i21avoyWmNMOr7guyg+amli0yY4Q3xCOwhHsJEGGvP6Z9BdWKLQ X-Received: by 2002:a63:2b82:: with SMTP id r124mr10729312pgr.300.1548442744202; Fri, 25 Jan 2019 10:59:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548442744; cv=none; d=google.com; s=arc-20160816; b=V1HxDl0tR5nZNEjwVVNs/x3nbyago8w7A5iZCRD9crlCFrVApx9YIRbIL+N50sUvhn 9yXHuFP9Jj35QyGmmm0E4HDS3By6pSNxvVnlY0Pv+KUASwsGMyBNE6UWBY1Q/jzbEhIZ YELFrEpuq7DaVsYvtjChaQyhjARIvnG57vnLFpJD/cVADccr+SSAzFGODnyzeoTvXppQ tFbrWMqZoyJw3YdsLamQcYCr0Djatsztp/3iRoRssXIEBGBdLJGDbuwuV6uFu1PAn22A br4x8XMDIIpqvyYS7lldwZcTmA8e2UHYW1jql3vG5E0X5gIxKLCtqjTV1dHyn5Xc1XFC NwPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=N6RKkHGUj8bJmjQqZYjUAS/y/wKQvr/C0iGdIoMKGek=; b=PIqDDqQIGNkhb9Z6eEAGwRzZ60X5LqDol4cnI/4lPcZjhZcaC3ZVdvTNJWp3+cxCqn llZcnpM58XiLo4uI4h9+UA9kekMEHUN1TpzGkdOE1o0Jm7z1uHpmHE2TVt5dN4Sa+gZK VaWwAK1SXvBHq52dlFJXMyELnSdicleJq4Zino1rdKFT41ckSF7C7IIkEPH1o4GMkTvL gsAzRlyHItm4nvWWCJkJhIyxOgSaaJuBOOMaVvtwqIT6hVfrIFbWyrIFnNKZKTv/GmXl OJHR3ATJP3ihhuL+F5RJY+UD7xtoGTy09RKvqXaPlIMNHtgEsqLyVT1y3I58SCP57s15 yIZQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 21si24815106pgk.74.2019.01.25.10.58.48; Fri, 25 Jan 2019 10:59:04 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726451AbfAYS6n (ORCPT + 99 others); Fri, 25 Jan 2019 13:58:43 -0500 Received: from mail-vs1-f68.google.com ([209.85.217.68]:38402 "EHLO mail-vs1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726044AbfAYS6n (ORCPT ); Fri, 25 Jan 2019 13:58:43 -0500 Received: by mail-vs1-f68.google.com with SMTP id x64so6282352vsa.5; Fri, 25 Jan 2019 10:58:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N6RKkHGUj8bJmjQqZYjUAS/y/wKQvr/C0iGdIoMKGek=; b=GFBc6NKcfybaEa/dK/cqMOZQNvh9iAZ+YfJw2XqgvJa676ulDyxlboe5omHGRF4byK zZFgm10gp4TWuxFtGo+4L18Bwuh6wwI33IgC5U9REeD2Ba1KTe+zzqXRL6xvj9ZFEnhn FzJKsLp+FI9ZgHm7/JohdSnGhHbK7Oswr+OvyvPiAGXIjZr4Hg+WYcuujOEgX1GzSv31 4HFDpLxjxGpSj+bSa4XEdRnX6wXtXU2mQHk0xko04ZvLGGqq/ShYosZUuC2kBMDTsqkt 5DnVUf8GMAFWXFjW7oY0QKdVee+IeqMMxxHSXdgCuSzI4+8t4EuZjaSwsE0IVYUHvnaZ 5FgQ== X-Gm-Message-State: AJcUuke+x+k74xr4XVQm3nLdaNqzSfXqkEgHOvYm+Eih3d20CyYTuc95 vyEqeN/VTF9SITr/Wbt3c6hng+9SbK9aWjJH85k= X-Received: by 2002:a67:f43:: with SMTP id 64mr5082621vsp.166.1548442722430; Fri, 25 Jan 2019 10:58:42 -0800 (PST) MIME-Version: 1.0 References: <20190125184640.5174-1-jcmvbkbc@gmail.com> In-Reply-To: <20190125184640.5174-1-jcmvbkbc@gmail.com> From: Geert Uytterhoeven Date: Fri, 25 Jan 2019 19:58:30 +0100 Message-ID: Subject: Re: [PATCH v2] treewide: get rid of HAVE_FUTEX_CMPXCHG To: Max Filippov Cc: LKML , Linux-Arch , Andy Lutomirski , Arnd Bergmann , Paul Burton , Ralf Baechle , Thomas Gleixner , Greg Ungerer Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Max, On Fri, Jan 25, 2019 at 7:47 PM Max Filippov wrote: > CONFIG_HAVE_FUTEX_CMPXCHG is currently used to determine if > atomic_inatomic is always working or must be probed. For most > architectures it is either selected, or it is known that they always > have futex_atomic_cmpxchg_inatomic working. > > Drop HAVE_FUTEX_CMPXCHG from the Kconfig and let architectures that may > not have it working define macro arch_have_futex_cmpxchg that probes > whether futex_atomic_cmpxchg_inatomic is working, otherwise assume that > it is working. > > Implement arch_have_futex_cmpxchg for MIPS, Xtensa and for the users of > asm-generic/futex.h. > > Cc: Andy Lutomirski > Cc: Arnd Bergmann > Cc: Geert Uytterhoeven > Cc: Paul Burton > Cc: Ralf Baechle > Cc: Thomas Gleixner > Suggested-by: Andy Lutomirski > Signed-off-by: Max Filippov > --- > Changes v1->v2: > - fix #ifdef/#ifndef logic in kernel/futex.c Thanks for the update! > arch/m68k/Kconfig | 1 - For m68k: Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds