[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOw6vbL7_KqKGA=OHMtUYvFZDwVr=PXYoFTzYtFH44qc-Au8WA@mail.gmail.com>
Date: Wed, 11 Oct 2017 16:28:39 -0400
From: Sean Paul <seanpaul@...omium.org>
To: Keith Packard <keithp@...thp.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Daniel Vetter <daniel.vetter@...el.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
David Airlie <airlied@...ux.ie>,
Ville Syrjälä <ville.syrjala@...ux.intel.com>,
Chris Wilson <chris@...is-wilson.co.uk>,
Alex Deucher <alexander.deucher@....com>,
Thierry Reding <treding@...dia.com>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] drm: vblank: use ktime_t instead of timeval
On Wed, Oct 11, 2017 at 4:18 PM, Keith Packard <keithp@...thp.com> wrote:
> Sean Paul <seanpaul@...omium.org> writes:
>
>> It looks like perhaps Keith missed one of the comment tweaks that you have
>> below.
>>
>> Keith, perhaps you can rebase your widening patch on this one?
>
> I'm easy; either order works for me just fine. Having the time
> change separated from the sequence change might be nice?
>
Yeah, that's what I was thinking. I'd normally default to first come
first serve, but since your patch is a superset, rebasing has the nice
feature of teasing out the widening change.
Would it be easier for you to respin this into your series, or for me
to just apply it to drm-misc-next?
Sean
> --
> -keith
Powered by blists - more mailing lists