From: Hugo Lefeuvre <hle@owl.eu.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Greg Hartman" <ghartman@google.com>,
"Alistair Strachan" <astrachan@google.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Christian Brauner" <christian@brauner.io>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"Joel Fernandes" <joel@joelfernandes.org>
Subject: [PATCH v2 0/2] sched/wait, staging/android: simplification of freeze related code
Date: Thu, 7 Feb 2019 22:28:19 +0100 [thread overview]
Message-ID: <cover.1549564792.git.hle@owl.eu.com> (raw)
This patchset introduces a new wait_event_freezable_hrtimeout method
to the wait api.
wait_event_freezable_hrtimeout is then used to greatly simplify
handle_vsoc_cond_wait in the android vsoc driver, reducing the
size of the vsoc driver.
Changes since v1 [1]:
- Delete "[1/3] sched/wait: use freezable_schedule when possible",
it was submitted separately.
- Patch 3/3 (now 2/2): Fix removal of a necessary linux/freezer.h
include and improve commit message.
[1] v1: https://lkml.org/lkml/2019/2/1/19
Hugo Lefeuvre (2):
sched/wait: introduce wait_event_freezable_hrtimeout
staging/android: simplify handle_vsoc_cond_wait
drivers/staging/android/vsoc.c | 68 +++++-----------------------------
include/linux/wait.h | 25 +++++++++++--
2 files changed, 31 insertions(+), 62 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-07 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 21:28 Hugo Lefeuvre [this message]
2019-02-07 21:29 ` [PATCH v2 1/2] sched/wait: introduce wait_event_freezable_hrtimeout Hugo Lefeuvre
2019-02-11 7:31 ` Ingo Molnar
2019-02-07 21:29 ` [PATCH v2 2/2] staging/android: simplify handle_vsoc_cond_wait Hugo Lefeuvre
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=cover.1549564792.git.hle@owl.eu.com \
--to=hle@owl.eu.com \
--cc=arve@android.com \
--cc=astrachan@google.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=ghartman@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tkjos@android.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 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.