From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Kees Cook <keescook@chromium.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PM: Convert timers to use timer_setup()
Date: Tue, 17 Oct 2017 02:15:11 +0200 [thread overview]
Message-ID: <58030006.IsIpgYu0sU@aspire.rjw.lan> (raw)
In-Reply-To: <CAGXu5j+S6WR_m0f5snY6NV0gt_OX7FCgi21d2uKYMYtoNMuuHw@mail.gmail.com>
On Tuesday, October 17, 2017 2:19:48 AM CEST Kees Cook wrote:
> On Mon, Oct 16, 2017 at 4:53 PM, Rafael J. Wysocki
> <rafael.j.wysocki@intel.com> wrote:
> > On 10/17/2017 1:20 AM, Kees Cook 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. Removes test of .data field, since
> >> that will be going away.
> >>
> >> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> >> Cc: Pavel Machek <pavel@ucw.cz>
> >> Cc: Len Brown <len.brown@intel.com>
> >> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> Cc: linux-pm@vger.kernel.org
> >> Signed-off-by: Kees Cook <keescook@chromium.org>
> >
> >
> > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Do you want this to be carried in the timers tree, or can you pick it up?
I can pick it up, but only for 4.15.
Thanks,
Rafael
next prev parent reply other threads:[~2017-10-17 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:20 [PATCH] PM: Convert timers to use timer_setup() Kees Cook
2017-10-16 23:53 ` Rafael J. Wysocki
2017-10-17 0:19 ` Kees Cook
2017-10-17 0:15 ` Rafael J. Wysocki [this message]
2017-10-17 0:30 ` 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=58030006.IsIpgYu0sU@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael.j.wysocki@intel.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).