From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kees Cook <keescook@chromium.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/selftests: Convert timers to use timer_setup()
Date: Wed, 25 Oct 2017 17:32:35 +0300 [thread overview]
Message-ID: <873767i9h8.fsf@intel.com> (raw)
In-Reply-To: <CAGXu5jKW9tt79i+2ii1ofKHyca=af-wF_AT7SH6TMNM36vhAsw@mail.gmail.com>
On Wed, 25 Oct 2017, Kees Cook <keescook@chromium.org> wrote:
> On Wed, Oct 25, 2017 at 4:16 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> Quoting Kees Cook (2017-10-25 15:05:13)
>>> On Wed, Oct 25, 2017 at 3:11 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>>> > Quoting Chris Wilson (2017-10-25 11:24:19)
>>> >> Quoting Chris Wilson (2017-10-24 17:17:09)
>>> >> > Quoting Kees Cook (2017-10-24 16:13:44)
>>> >> > > 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: Jani Nikula <jani.nikula@linux.intel.com>
>>> >> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>>> >> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> >> > > Cc: David Airlie <airlied@linux.ie>
>>> >> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> >> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
>>> >> > > Cc: intel-gfx@lists.freedesktop.org
>>> >> > > Cc: dri-devel@lists.freedesktop.org
>>> >> > > Signed-off-by: Kees Cook <keescook@chromium.org>
>>> >> >
>>> >> > Thank you for saving me from having to do this myself,
>>> >> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> >>
>>> >> I've a small batch of selftests patches queued, so added this one and
>>> >> will push to drm-intel-next-queued shortly.
>>> >
>>> > Oh dear, major faux pas. There is no timer_setup_on_stack yet.
>>>
>>> Argh. Right, sorry. That's only in -next. Since this is mainly a
>>> mechanical change, should I carry this in the timer tree, or wait
>>> until the merge window for it to go via i915?
>>
>> Jani has the final word, but my understanding is that there will be no
>> more from i915 towards the 4.15 merge. Hmm, the origin of this timer,
>>
>> commit 214707fc2ce08d09982bc4fe4b7a1c1f010e82be
>> Author: Chris Wilson <chris@chris-wilson.co.uk>
>> Date: Thu Oct 12 13:57:25 2017 +0100
>>
>> drm/i915/selftests: Wrap a timer into a i915_sw_fence
>>
>> did make it into 4.15, so it would have been better to put into a
>> separate tree for the 4.15 merge window anyway. In hindsight, yes this
>> probably wants to be carried in the timer tree to be applied after i915.
>> (I guess there will be a few other stragglers that need to be converted
>> at the end of the merge window anyway.)
>
> Yeah, it's going to be messy, but I'll manage. I'll be carrying a lot
> of other stuff as well. Avoiding conflicts will be the trick. Wheee.
> :)
Acked-by: Jani Nikula <jani.nikula@intel.com>
for merging via timer tree. Otherwise we'll need to wait for the changes
to hit Linus' tree, then get backmerges to our tree, and it's v4.16
before you know it. ;)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kees Cook <keescook@chromium.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
intel-gfx@lists.freedesktop.org,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/selftests: Convert timers to use timer_setup()
Date: Wed, 25 Oct 2017 17:32:35 +0300 [thread overview]
Message-ID: <873767i9h8.fsf@intel.com> (raw)
In-Reply-To: <CAGXu5jKW9tt79i+2ii1ofKHyca=af-wF_AT7SH6TMNM36vhAsw@mail.gmail.com>
On Wed, 25 Oct 2017, Kees Cook <keescook@chromium.org> wrote:
> On Wed, Oct 25, 2017 at 4:16 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> Quoting Kees Cook (2017-10-25 15:05:13)
>>> On Wed, Oct 25, 2017 at 3:11 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>>> > Quoting Chris Wilson (2017-10-25 11:24:19)
>>> >> Quoting Chris Wilson (2017-10-24 17:17:09)
>>> >> > Quoting Kees Cook (2017-10-24 16:13:44)
>>> >> > > 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: Jani Nikula <jani.nikula@linux.intel.com>
>>> >> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>>> >> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> >> > > Cc: David Airlie <airlied@linux.ie>
>>> >> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> >> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
>>> >> > > Cc: intel-gfx@lists.freedesktop.org
>>> >> > > Cc: dri-devel@lists.freedesktop.org
>>> >> > > Signed-off-by: Kees Cook <keescook@chromium.org>
>>> >> >
>>> >> > Thank you for saving me from having to do this myself,
>>> >> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> >>
>>> >> I've a small batch of selftests patches queued, so added this one and
>>> >> will push to drm-intel-next-queued shortly.
>>> >
>>> > Oh dear, major faux pas. There is no timer_setup_on_stack yet.
>>>
>>> Argh. Right, sorry. That's only in -next. Since this is mainly a
>>> mechanical change, should I carry this in the timer tree, or wait
>>> until the merge window for it to go via i915?
>>
>> Jani has the final word, but my understanding is that there will be no
>> more from i915 towards the 4.15 merge. Hmm, the origin of this timer,
>>
>> commit 214707fc2ce08d09982bc4fe4b7a1c1f010e82be
>> Author: Chris Wilson <chris@chris-wilson.co.uk>
>> Date: Thu Oct 12 13:57:25 2017 +0100
>>
>> drm/i915/selftests: Wrap a timer into a i915_sw_fence
>>
>> did make it into 4.15, so it would have been better to put into a
>> separate tree for the 4.15 merge window anyway. In hindsight, yes this
>> probably wants to be carried in the timer tree to be applied after i915.
>> (I guess there will be a few other stragglers that need to be converted
>> at the end of the merge window anyway.)
>
> Yeah, it's going to be messy, but I'll manage. I'll be carrying a lot
> of other stuff as well. Avoiding conflicts will be the trick. Wheee.
> :)
Acked-by: Jani Nikula <jani.nikula@intel.com>
for merging via timer tree. Otherwise we'll need to wait for the changes
to hit Linus' tree, then get backmerges to our tree, and it's v4.16
before you know it. ;)
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-10-25 14:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 15:13 [PATCH] drm/i915/selftests: Convert timers to use timer_setup() Kees Cook
2017-10-24 15:13 ` Kees Cook
2017-10-24 16:17 ` Chris Wilson
2017-10-24 16:17 ` Chris Wilson
2017-10-25 10:24 ` Chris Wilson
2017-10-25 10:24 ` Chris Wilson
2017-10-25 13:11 ` Chris Wilson
2017-10-25 13:11 ` Chris Wilson
2017-10-25 14:05 ` Kees Cook
2017-10-25 14:05 ` Kees Cook
2017-10-25 14:16 ` Chris Wilson
2017-10-25 14:27 ` Kees Cook
2017-10-25 14:27 ` Kees Cook
2017-10-25 14:32 ` Jani Nikula [this message]
2017-10-25 14:32 ` Jani Nikula
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=873767i9h8.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@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 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.