public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "alexdeucher@gmail.com" <alexdeucher@gmail.com>
Cc: "daniel@ffwll.ch" <daniel@ffwll.ch>,
	"Jose.Abreu@synopsys.com" <Jose.Abreu@synopsys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"CARLOS.PALMINHA@synopsys.com" <CARLOS.PALMINHA@synopsys.com>,
	"daniel.vetter@intel.com" <daniel.vetter@intel.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>
Subject: Re: Please pull ARCPGU changes
Date: Wed, 2 Aug 2017 21:21:32 +0000	[thread overview]
Message-ID: <1501708891.2864.5.camel@synopsys.com> (raw)
In-Reply-To: <CADnq5_OSnPGKv35Aogf8pmtoH=w8pDKwttf3hW6MD9=s=yhZjw@mail.gmail.com>

Hi Alex,

On Wed, 2017-08-02 at 14:24 -0400, Alex Deucher wrote:
> On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> > 
> > 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?
> 
> next:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_-7Eairlied_linux_log_-3Fh-3Ddrm-2Dnext&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r
> =lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=pbG-5bjYHB5-5W7BvTn5O7AaB-7boN5rb88XcxgLT5s&s=WrBr72Zx251yCmFMiv7mH7uKt5omhSWk8vlr0GDvG60&e= 
> 
> fixes:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_-7Eairlied_linux_log_-3Fh-3Ddrm-2Dfixes&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&
> r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=pbG-5bjYHB5-5W7BvTn5O7AaB-7boN5rb88XcxgLT5s&s=iRx0mpfiNcQURDcMGyXfb9arq0OQsCnMddGvXDVk7Zg&e= 

I added this repo as a remote and sent new pull-request based on drm-next.

Thanks a lot for your help.

-Alexey

  reply	other threads:[~2017-08-02 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 11:11 Please pull ARCPGU changes Alexey Brodkin
2017-08-02  9:41 ` Daniel Vetter
2017-08-02 10:16   ` Alexey Brodkin
2017-08-02 18:24     ` Alex Deucher
2017-08-02 21:21       ` Alexey Brodkin [this message]
2017-08-02 21:20 ` [PULL] " Alexey Brodkin

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=1501708891.2864.5.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=alexdeucher@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    /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