[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20170115230016.GA14446@mtj.duckdns.org>
Date: Sun, 15 Jan 2017 18:00:16 -0500
From: Tejun Heo <tj@...nel.org>
To: efault@....de, axboe@...nel.dk, peterz@...radead.org,
mingo@...nel.org, hpa@...or.com, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
tglx@...utronix.de
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] locking/mutex, sched/wait: Fix the
mutex_lock_io_nested() define
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 <mingo@...nel.org>
> AuthorDate: Sat, 14 Jan 2017 17:11:36 +0100
> Committer: Ingo Molnar <mingo@...nel.org>
> 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
Powered by blists - more mailing lists