From: Greg KH <greg@kroah.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: stable@vger.kernel.org, bigeasy@linutronix.de,
bristot@redhat.com, Darren Hart <dvhart@infradead.org>,
jdesfossez@efficios.com, juri.lelli@arm.com,
mathieu.desnoyers@efficios.com, rostedt@goodmis.org,
xlpang@redhat.com
Subject: Re: [PATCH 4.4 00/10] [Set 2] Futex back-port
Date: Fri, 5 Feb 2021 09:55:53 +0100 [thread overview]
Message-ID: <YB0IGXv+vC45mU0S@kroah.com> (raw)
In-Reply-To: <20210204172903.2860981-1-lee.jones@linaro.org>
On Thu, Feb 04, 2021 at 05:28:53PM +0000, Lee Jones wrote:
> This set required 4 additional patches to avoid errors.
>
> Peter Zijlstra (4):
> futex,rt_mutex: Provide futex specific rt_mutex API
> futex: Remove rt_mutex_deadlock_account_*()
> futex: Rework inconsistent rt_mutex/futex_q state
> futex: Avoid violating the 10th rule of futex
>
> Thomas Gleixner (6):
> futex: Replace pointless printk in fixup_owner()
> futex: Provide and use pi_state_update_owner()
> rtmutex: Remove unused argument from rt_mutex_proxy_unlock()
> futex: Use pi_state_update_owner() in put_pi_state()
> futex: Simplify fixup_pi_state_owner()
> futex: Handle faults correctly for PI futexes
All now queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-02-05 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 17:28 [PATCH 4.4 00/10] [Set 2] Futex back-port Lee Jones
2021-02-04 17:28 ` [PATCH 01/10] futex,rt_mutex: Provide futex specific rt_mutex API Lee Jones
2021-02-04 17:28 ` [PATCH 02/10] futex: Remove rt_mutex_deadlock_account_*() Lee Jones
2021-02-04 17:28 ` [PATCH 03/10] futex: Rework inconsistent rt_mutex/futex_q state Lee Jones
2021-02-04 17:28 ` [PATCH 04/10] futex: Avoid violating the 10th rule of futex Lee Jones
2021-02-04 17:28 ` [PATCH 05/10] futex: Replace pointless printk in fixup_owner() Lee Jones
2021-02-04 17:28 ` [PATCH 06/10] futex: Provide and use pi_state_update_owner() Lee Jones
2021-02-07 22:16 ` Ben Hutchings
2021-02-04 17:29 ` [PATCH 07/10] rtmutex: Remove unused argument from rt_mutex_proxy_unlock() Lee Jones
2021-02-04 17:29 ` [PATCH 08/10] futex: Use pi_state_update_owner() in put_pi_state() Lee Jones
2021-02-04 17:29 ` [PATCH 09/10] futex: Simplify fixup_pi_state_owner() Lee Jones
2021-02-04 17:29 ` [PATCH 10/10] futex: Handle faults correctly for PI futexes Lee Jones
2021-02-05 8:55 ` Greg KH [this message]
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=YB0IGXv+vC45mU0S@kroah.com \
--to=greg@kroah.com \
--cc=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=dvhart@infradead.org \
--cc=jdesfossez@efficios.com \
--cc=juri.lelli@arm.com \
--cc=lee.jones@linaro.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=xlpang@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).