All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	James Qian Wang <james.qian.wang@arm.com>,
	DRI devel <dri-devel@lists.freedesktop.org>,
	MaliDP Maintainers <malidp@foss.arm.com>
Subject: Re: [PULL] 2nd pull for malidp-next
Date: Fri, 3 May 2019 10:50:24 +0100	[thread overview]
Message-ID: <20190503095024.GD15144@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAPM=9txjGu8NxGROVcfRuZ_PhqY8Q2VHZaA_1cuwO9K3wccG6g@mail.gmail.com>

On Fri, May 03, 2019 at 09:54:35AM +1000, Dave Airlie wrote:
> On Thu, 2 May 2019 at 20:45, Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> >
> > Hi DRM maintainers,
> >
> > This is the 2nd pull request for the malidp-next. The new patches add
> > additional support for Arm Mali D71 so that it can now be enabled
> > correctly and brought up on any SoC that contains the IP. From now on
> > we will start focusing on adding writeback, scaling and other useful
> > features to bring the driver to the same level of maturity as mali-dp.
> >
> > Please pull,
> > Liviu
> >
> >
> >
> > The following changes since commit 7c13e5cc2391950541f41fc9ab0336aae77c7f63:
> >
> >   Merge tag 'drm-intel-next-fixes-2019-04-25' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2019-04-26 11:35:59 +1000)
> >
> > are available in the Git repository at:
> >
> >   git://linux-arm.org/linux-ld.git for-upstream/mali-dp
> 
> This branch contains:
> commit 04c8a1ec395b22f060b836b72d2d4480e7e859f8
> Author: Liviu Dudau <Liviu.Dudau@arm.com>
> Date:   Tue Mar 26 10:23:40 2019 +0000
> 
>     MAINTAINERS: Fix pattern for Documentation path for Arm Mali Komeda
> 
> as it's head, did you forget to push?

Sorry about that, it looks like I've head another refspec with the same
name, it should have pointed to refs/heads/for-upstream/mali-dp. I
should have now sorted it.

Best regards,
Liviu


> 
> Dave.

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2019-05-03  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 10:45 [PULL] 2nd pull for malidp-next Liviu Dudau
2019-05-02 23:54 ` Dave Airlie
2019-05-03  9:11   ` Liviu Dudau
2019-05-03  9:15     ` Daniel Vetter
2019-05-03  9:29       ` Liviu Dudau
2019-05-03 12:17         ` Daniel Vetter
2019-05-06 23:50           ` Dave Airlie
2019-05-07 10:37             ` Liviu Dudau
2019-05-03  9:47       ` Liviu Dudau
2019-05-03  9:50   ` Liviu Dudau [this message]

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=20190503095024.GD15144@e110455-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=james.qian.wang@arm.com \
    --cc=malidp@foss.arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.