From: Peter Zijlstra <peterz@infradead.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: akpm@linux-foundation.org, mingo@redhat.com,
keescook@chromium.org, dmitry.torokhov@gmail.com,
jeyu@redhat.com, rusty@rustcorp.com.au, mmarek@suse.com,
pmladek@suse.com, mbenes@suse.cz, jpoimboe@redhat.com,
ebiederm@xmission.com, shuah@kernel.org,
matt.redfearn@imgtec.com, dan.carpenter@oracle.com,
colin.king@canonical.com, danielmentz@google.com,
dcb314@hotmail.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] wait: add wait_event_killable_timeout()
Date: Thu, 10 Aug 2017 12:33:05 +0200 [thread overview]
Message-ID: <20170810103305.gz5dwbal3rkvc7uu@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170809234635.13443-2-mcgrof@kernel.org>
On Wed, Aug 09, 2017 at 04:46:33PM -0700, Luis R. Rodriguez wrote:
> This wait is similar to wait_event_interruptable_timeout() but only accepts
> SIGKILL interrupt signal. Other signals are ignored.
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
Assuming someone else is going to merge all these:
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2017-08-10 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 23:46 [PATCH 0/3] kmod: pending fixes for v4.13-final Luis R. Rodriguez
2017-08-09 23:46 ` [PATCH 1/3] wait: add wait_event_killable_timeout() Luis R. Rodriguez
2017-08-10 10:33 ` Peter Zijlstra [this message]
2017-08-09 23:46 ` [PATCH 2/3] kmod: fix wait on recursive loop Luis R. Rodriguez
2017-08-09 23:46 ` [PATCH 3/3] test_kmod: fix description for -s -and -c parameters Luis R. Rodriguez
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=20170810103305.gz5dwbal3rkvc7uu@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=danielmentz@google.com \
--cc=dcb314@hotmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jeyu@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matt.redfearn@imgtec.com \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=pmladek@suse.com \
--cc=rusty@rustcorp.com.au \
--cc=shuah@kernel.org \
/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).