linux-kernel - Re: Please pull ARCPGU changes

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]

Message-ID: <1501668977.6345.35.camel@synopsys.com>
Date:   Wed, 2 Aug 2017 10:16:18 +0000
From:   Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To:     "daniel@...ll.ch" <daniel@...ll.ch>
CC:     "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "airlied@...il.com" <airlied@...il.com>,
        "Jose.Abreu@...opsys.com" <Jose.Abreu@...opsys.com>,
        "CARLOS.PALMINHA@...opsys.com" <CARLOS.PALMINHA@...opsys.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "daniel.vetter@...el.com" <daniel.vetter@...el.com>,
        "linux-snps-arc@...ts.infradead.org" 
        <linux-snps-arc@...ts.infradead.org>
Subject: Re: Please pull ARCPGU changes

Hi Daniel,

On Wed, 2017-08-02 at 11:41 +0200, Daniel Vetter wrote:
> On Mon, Jul 31, 2017 at 11:11:06AM +0000, Alexey Brodkin wrote:
> > 
> > Hi Dave,
> > 
> > Could you please pull a couple of minor fixes for ARCPGU.
> > These changes are based on today's drm-misc/drm-misc-next.
> 
> You can't send Dave a pull based on a random snapshot of drm-misc-next. If
> you want to maintain your driver on top of drm-misc, then become part of
> the group (arcgpu would fit imo). Otherwise you need to base your pulls on
> top of Dave's tree.

I don't have any specific requirement for "drm-misc-next" to b used as a base.
That said Dave trees are OK for me. Still could you please point me to
his "for-curr" and "for-next" (or equivalent) trees?

> Also, your pull is missing the [PULL] tag in the
> subject.

Sorry for that, will fix it in the next request.

-Alexey