From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/sclp: Convert timers to use timer_setup()
Date: Tue, 17 Oct 2017 10:59:10 +0200 [thread overview]
Message-ID: <20171017105910.5735a5b9@mschwideX1> (raw)
In-Reply-To: <20171016234430.GA102114@beast>
On Mon, 16 Oct 2017 16:44:30 -0700
Kees Cook <keescook@chromium.org> wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly. Instead of creating an external static
> data variable, just define a separate callback which encodes the "force
> restart" desire.
>
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> Cc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-s390@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> drivers/s390/char/con3215.c | 6 +++---
> drivers/s390/char/con3270.c | 10 +++++-----
> drivers/s390/char/sclp.c | 45 ++++++++++++++++++++++++------------------
> drivers/s390/char/sclp_con.c | 5 ++---
> drivers/s390/char/sclp_tty.c | 5 ++---
> drivers/s390/char/sclp_vt220.c | 6 ++----
> drivers/s390/char/tape_core.c | 14 ++++---------
> drivers/s390/char/tty3270.c | 8 ++++----
> 8 files changed, 48 insertions(+), 51 deletions(-)
Applied to s390/linux:feature branch. Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2017-10-17 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:44 [PATCH] s390/sclp: Convert timers to use timer_setup() Kees Cook
2017-10-17 8:59 ` Martin Schwidefsky [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=20171017105910.5735a5b9@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.vnet.ibm.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