From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: mtk.manpages@gmail.com, Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
Darren Hart <darren@dvhart.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 2/2] futex: Fix argument handling in futex_lock_pi() calls
Date: Sat, 17 Jan 2015 09:42:11 +0100 [thread overview]
Message-ID: <54BA2063.1020702@gmail.com> (raw)
In-Reply-To: <20150117020401.GB6494@vmdeb7>
On 01/17/2015 03:04 AM, Darren Hart wrote:
> On Fri, Jan 16, 2015 at 08:28:06PM +0100, Michael Kerrisk (man-pages) wrote:
>> From: Michael Kerrisk <mtk.manpages@gmail.com>
>>
>> This patch fixes two separate buglets in calls to futex_lock_pi():
>>
>> * Eliminate unused 'detect' argument
>> * Change unused 'timeout' argument of FUTEX_TRYLOCK_PI to NULL
>
> One might argue these should be two separate fixes. Since both are trivial and functional
> no-ops, I'm going to ignore it and consider it a "cleanup" :-) Thomas may
> disagree.
Yup, and that's what I was going to do until I realized that the patches
changed the same line. Then I thought it easier to combine them (rather
than make dependent patches), since they're fairly trivial. But,
I'll split them if Thomas wishes.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2015-01-17 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 19:28 [PATCH 2/2] futex: Fix argument handling in futex_lock_pi() calls Michael Kerrisk (man-pages)
2015-01-17 2:04 ` Darren Hart
2015-01-17 8:42 ` Michael Kerrisk (man-pages) [this message]
2015-01-19 11:10 ` [tip:locking/core] futex: Fix argument handling in futex_lock_pi( ) calls tip-bot for Michael Kerrisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BA2063.1020702@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=darren@dvhart.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.