From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
James Qian Wang <james.qian.wang@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
DRI devel <dri-devel@lists.freedesktop.org>,
MaliDP Maintainers <malidp@foss.arm.com>
Subject: Re: [PULL] 2nd pull for malidp-next
Date: Tue, 7 May 2019 09:50:19 +1000 [thread overview]
Message-ID: <CAPM=9tweO7C0EiLdC-fMDaozyX4ds9arsCRqxziYDZufFOEAfw@mail.gmail.com> (raw)
In-Reply-To: <20190503121753.GM3271@phenom.ffwll.local>
On Fri, 3 May 2019 at 22:17, Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Fri, May 03, 2019 at 10:29:48AM +0100, Liviu Dudau wrote:
> > On Fri, May 03, 2019 at 11:15:23AM +0200, Daniel Vetter wrote:
> > > On Fri, May 3, 2019 at 11:11 AM Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> > > >
> > > > 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
So I get commits now, but I also get:
Pulling git://linux-arm.org/linux-ld.git for-upstream/mali-dp ...
From git://linux-arm.org/linux-ld
* branch for-upstream/mali-dp -> FETCH_HEAD
dim: 09918bb1ff8c ("drm/komeda: Use memset to initialize config_id"):
SHA1 in fixes line not found:
dim: 4cc734cb79a8 ("drm/komeda: Add sysfs attribute: core_id and config_id")
dim: d9fcab4a131d ("drm/komeda: Mark the local functions as static"):
author Signed-off-by missing.
dim: ERROR: issues in commits detected, aborting
Please fix the fixes tag, though since that is all in the one pull
request you should probably squash the fix into the offending commit.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-06 23: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 [this message]
2019-05-07 10:37 ` Liviu Dudau
2019-05-03 9:47 ` Liviu Dudau
2019-05-03 9:50 ` Liviu Dudau
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='CAPM=9tweO7C0EiLdC-fMDaozyX4ds9arsCRqxziYDZufFOEAfw@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=Liviu.Dudau@arm.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@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.