From: Kees Cook <keescook@chromium.org>
To: Kees Cook <keescook@chromium.org>,
Patrik Jakobsson <patrik.r.jakobsson@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: gma500: Convert timers to use timer_setup()
Date: Mon, 30 Oct 2017 15:05:29 -0700 [thread overview]
Message-ID: <CAGXu5jLx8VanJTej4BC-Mko=3n1HMGgRV_KajWWM0b50xt350g@mail.gmail.com> (raw)
In-Reply-To: <20171030100838.lvjxy3o6q227kjsn@phenom.ffwll.local>
On Mon, Oct 30, 2017 at 3:08 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Oct 24, 2017 at 08:16:09AM -0700, 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.
>>
>> Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
>> Cc: David Airlie <airlied@linux.ie>
>> Cc: dri-devel@lists.freedesktop.org
>> Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Do you expect drm folks to apply this, or is this part of a larger refactoring?
If the drm tree includes -rc3, you can carry these. If you don't want
to carry these and want the timer tree to carry them, we can do that
too.
> A notch more context in the commit message would help ...
Sorry about that, my added context for this go lost in later conversion patches.
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2017-10-30 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 15:16 [PATCH] drm: gma500: Convert timers to use timer_setup() Kees Cook
2017-10-30 10:08 ` Daniel Vetter
2017-10-30 22:05 ` Kees Cook [this message]
2017-10-31 10:18 ` Daniel Vetter
2017-10-31 15:08 ` Kees Cook
2017-11-01 9:02 ` Daniel Vetter
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='CAGXu5jLx8VanJTej4BC-Mko=3n1HMGgRV_KajWWM0b50xt350g@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.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).