Re: [tip:sched/core] locking/mutex, sched/wait: Add mutex_lock_io()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Mike Galbraith <efault@xxxxxx> wrote:

> On Sat, 2017-01-14 at 04:50 -0800, tip-bot for Tejun Heo wrote:
> 
> > diff --git a/include/linux/mutex.h b/include/linux/mutex.h
> > index b97870f..980ba16 100644
> > --- a/include/linux/mutex.h
> > +++ b/include/linux/mutex.h
> 
> > @@ -171,11 +173,13 @@ do {									\
> >  extern void mutex_lock(struct mutex *lock);
> >  extern int __must_check mutex_lock_interruptible(struct mutex *lock);
> >  extern int __must_check mutex_lock_killable(struct mutex *lock);
> > +extern void mutex_lock_io(struct mutex *lock);
> >  
> >  # define mutex_lock_nested(lock, subclass) mutex_lock(lock)
> >  # define mutex_lock_interruptible_nested(lock, subclass) mutex_lock_interruptible(lock)
> >  # define mutex_lock_killable_nested(lock, subclass) mutex_lock_killable(lock)
> >  # define mutex_lock_nest_lock(lock, nest_lock) mutex_lock(lock)
> > +# define mutex_lock_nest_io(lock, nest_lock) mutex_io(lock)
>                                                 ^^^^^^^^^^^^^^ typo

Double typo in fact I think, that should be something like:

# define mutex_lock_io_nested(lock, subclass) mutex_lock(lock)

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux