lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 12 Oct 2017 09:04:13 -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 04:28:39PM -0400, Sean Paul wrote:
> 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?
> 

It seems like we have consensus, and Daniel has offered to pick both of Arnd's
patches into -misc-next.

So thanks to Keith for being flexible, and

Reviewed-by: Sean Paul <seanpaul@...omium.org>

Sean


> Sean
> 
> 
> > --
> > -keith

-- 
Sean Paul, Software Engineer, Google / Chromium OS

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ