From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: Kees Cook <keescook@chromium.org>,
David Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/vc4: Convert timers to use timer_setup()
Date: Mon, 6 Nov 2017 09:39:09 +0100 [thread overview]
Message-ID: <20171106083908.vferyw7li4taesgl@phenom.ffwll.local> (raw)
In-Reply-To: <87a803ruqq.fsf@anholt.net>
On Fri, Nov 03, 2017 at 01:07:57PM -0700, Eric Anholt wrote:
> Kees Cook <keescook@chromium.org> writes:
>
> > On Mon, Oct 30, 2017 at 4:49 PM, Eric Anholt <eric@anholt.net> wrote:
> >> Kees Cook <keescook@chromium.org> writes:
> >>
> >>> 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.
> >>
> >> Reviewed and applied to drm-misc-next. Thanks!
> >
> > Thanks!
> >
> > I happened to notice that this was in next-20171102, but missing in
> > next-20171103. Did it get removed, or am I misunderstanding something?
>
> I don't know. It's in drm-misc-next, though, so it'll flow upstream
> without my intervention.
I'll make 4.16. Again, our merge cutoff is -rc6, hence why they all
missed. I guess one more to cherry-pick for you, or time to give up?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2017-11-06 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 15:16 [PATCH] drm/vc4: Convert timers to use timer_setup() Kees Cook
2017-10-30 23:49 ` Eric Anholt
2017-11-03 19:27 ` Kees Cook
2017-11-03 20:07 ` Eric Anholt
2017-11-06 8:39 ` Daniel Vetter [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=20171106083908.vferyw7li4taesgl@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.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).