From: "Keith Packard" <keithp@keithp.com>
To: Sean Paul <seanpaul@chromium.org>, Arnd Bergmann <arnd@arndb.de>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Sean Paul" <seanpaul@chromium.org>,
"David Airlie" <airlied@linux.ie>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Thierry Reding" <treding@nvidia.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm: vblank: use ktime_t instead of timeval
Date: Wed, 11 Oct 2017 13:18:41 -0700 [thread overview]
Message-ID: <87376p8mla.fsf@keithp.com> (raw)
In-Reply-To: <20171011173642.ivbyzxqk3qtuysar@art_vandelay>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Sean Paul <seanpaul@chromium.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?
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-11 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 15:20 [PATCH 1/2] drm: vblank: use ktime_t instead of timeval Arnd Bergmann
2017-10-11 15:20 ` [PATCH 2/2] drm: vblank: remove drm_timestamp_monotonic parameter Arnd Bergmann
2017-10-11 15:40 ` Daniel Stone
2017-10-11 17:36 ` [PATCH 1/2] drm: vblank: use ktime_t instead of timeval Sean Paul
2017-10-11 19:00 ` Arnd Bergmann
2017-10-11 20:17 ` Keith Packard
2017-10-11 20:18 ` Keith Packard [this message]
2017-10-11 20:28 ` Sean Paul
2017-10-11 21:07 ` Keith Packard
2017-10-12 13:04 ` Sean Paul
2017-10-12 18:20 ` Keith Packard
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=87376p8mla.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=arnd@arndb.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=treding@nvidia.com \
--cc=ville.syrjala@linux.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).