From: Christian Gmeiner <christian.gmeiner@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>,
Sascha Hauer <kernel@pengutronix.de>,
The etnaviv authors <etnaviv@lists.freedesktop.org>
Subject: Re: [GIT PULL] etnaviv-next for 4.21
Date: Mon, 17 Dec 2018 11:09:49 +0100 [thread overview]
Message-ID: <CAH9NwWeP2z9mnjhQRJofGs6miyUzbVoGwQvr5DLVy+voqhCJSQ@mail.gmail.com> (raw)
In-Reply-To: <1544784250.3137.43.camel@pengutronix.de>
Am Fr., 14. Dez. 2018 um 11:44 Uhr schrieb Lucas Stach <l.stach@pengutronix.de>:
>
> Hi Dave,
>
> nothing major this time, mostly some cleanups that were found on the
> way of reworking the code in preparation for new feature additions.
>
> Regards,
> Lucas
>
> The following changes since commit 6fce3a406108ee6c8a61e2a33e52e9198a626ea0:
>
> drm/etnaviv: fix bogus fence complete check in timeout handler (2018-11-05 18:14:48 +0100)
>
> are available in the Git repository at:
>
> https://git.pengutronix.de/git/lst/linux etnaviv/next
>
> for you to fetch changes up to dea492e0cfcbe8ca592406fefc7ceeaf53f63380:
>
> drm/etnaviv: remove lastctx member from gpu struct (2018-12-11 12:35:07 +0100)
>
> ----------------------------------------------------------------
> Lucas Stach (5):
..
> drm/etnaviv: remove unnecessary local irq disable
> drm/etnaviv: replace header include with forward declaration
> drm/etnaviv: remove lastctx member from gpu struct
>
I did not found these three patches via google or in my in-box. Where
they ever send to any ml?
greets
--
Christian Gmeiner, MSc
https://christian-gmeiner.info
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-12-17 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 10:44 [GIT PULL] etnaviv-next for 4.21 Lucas Stach
2018-12-14 22:11 ` Daniel Vetter
2018-12-17 9:50 ` Daniel Vetter
2018-12-17 10:09 ` Christian Gmeiner [this message]
2018-12-17 15:37 ` Lucas Stach
2018-12-17 16:24 ` Daniel Vetter
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=CAH9NwWeP2z9mnjhQRJofGs6miyUzbVoGwQvr5DLVy+voqhCJSQ@mail.gmail.com \
--to=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
/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.