From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Harald Freudenberger <freude@de.ibm.com>,
linux-s390@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] s390/ap_bus: Convert timers to use timer_setup()
Date: Fri, 3 Nov 2017 07:29:26 +0100 [thread overview]
Message-ID: <20171103072926.12ef827c@mschwideX1> (raw)
In-Reply-To: <CAGXu5jLJY_zYf=v_xYUEG6tgLzwvW8P+-d9GNNp8XN5bhnWvzQ@mail.gmail.com>
On Thu, 2 Nov 2017 16:36:53 -0700
Kees Cook <keescook@chromium.org> wrote:
> On Wed, Oct 25, 2017 at 11:38 PM, Martin Schwidefsky
> <schwidefsky@de.ibm.com> wrote:
> > On Wed, 25 Oct 2017 03:27:37 -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.
> >>
> >> Cc: Harald Freudenberger <freude@de.ibm.com>
> >> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> >> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> >> Cc: linux-s390@vger.kernel.org
> >> Signed-off-by: Kees Cook <keescook@chromium.org>
> >> ---
> >> drivers/s390/crypto/ap_bus.c | 10 +++++-----
> >> drivers/s390/crypto/ap_bus.h | 2 +-
> >> drivers/s390/crypto/ap_queue.c | 2 +-
> >> 3 files changed, 7 insertions(+), 7 deletions(-)
> >
> > Parked for the second part of the s390 updates for the next merge window.
> > Thanks.
>
> Thanks for getting these staged. I just wanted to check with you,
> since I don't see these in -next anywhere yet:
>
> s390: qdio: Convert timers to use timer_setup()
> s390/sclp: Convert timers to use timer_setup()
> s390/cio: Convert timers to use timer_setup()
> s390/scsi: Convert timers to use timer_setup()
> s390/ap_bus: Convert timers to use timer_setup()
>
> Are all of these expected to land for -rc1? (Would it help to carry
> them in the timer tree?) I've got tree-wide changes ready to go once
> all these conversions have landed.
These patches are parked on a private branches. The features branch
on s390/linux is the one that is used for -next AND for the upstream
merge. And since I do not want to rebase that branch the timer_setup
patches are not in -next as well.
Four of you patches are safe with me, the s390/scsi patch is in
Steffens patch queue. All good I would say.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2017-11-03 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 10:27 [PATCH] s390/ap_bus: Convert timers to use timer_setup() Kees Cook
2017-10-26 6:38 ` Martin Schwidefsky
2017-11-02 23:36 ` Kees Cook
2017-11-03 6:29 ` Martin Schwidefsky [this message]
2017-11-03 20:36 ` Kees Cook
2017-11-16 7:58 ` Kees Cook
2017-11-16 8:03 ` Martin Schwidefsky
2017-11-16 8:03 ` Kees Cook
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=20171103072926.12ef827c@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=freude@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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.