From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751347AbdAOXAW (ORCPT ); Sun, 15 Jan 2017 18:00:22 -0500 Received: from mail-it0-f66.google.com ([209.85.214.66]:36437 "EHLO mail-it0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbdAOXAU (ORCPT ); Sun, 15 Jan 2017 18:00:20 -0500 Date: Sun, 15 Jan 2017 18:00:16 -0500 From: Tejun Heo To: efault@gmx.de, axboe@kernel.dk, peterz@infradead.org, mingo@kernel.org, hpa@zytor.com, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, tglx@linutronix.de Cc: linux-tip-commits@vger.kernel.org Subject: Re: [tip:sched/core] locking/mutex, sched/wait: Fix the mutex_lock_io_nested() define Message-ID: <20170115230016.GA14446@mtj.duckdns.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 15, 2017 at 01:26:16AM -0800, tip-bot for Ingo Molnar wrote: > Commit-ID: f21860bac05b609d71757338361d26209ff0759b > Gitweb: http://git.kernel.org/tip/f21860bac05b609d71757338361d26209ff0759b > Author: Ingo Molnar > AuthorDate: Sat, 14 Jan 2017 17:11:36 +0100 > Committer: Ingo Molnar > CommitDate: Sat, 14 Jan 2017 17:11:36 +0100 > > locking/mutex, sched/wait: Fix the mutex_lock_io_nested() define > > Mike noticed this bogosity: > > > > +# define mutex_lock_nest_io(lock, nest_lock) mutex_io(lock) > > ^^^^^^^^^^^^^^ typo > > This new locking API is not used yet, so this didn't trigger in testing. > > Fix it. Oops, thanks! -- tejun