From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Daniel Vetter <daniel.vetter@intel.com>,
Thierry Reding <treding@nvidia.com>,
David Herrmann <dh.herrmann@gmail.com>,
"Syrjala, Ville" <ville.syrjala@linux.intel.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Archit Taneja <architt@codeaurora.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
Chris Wilson <chris@chris-wilson.co.uk>,
Kristian Kristensen <hoegsberg@google.com>,
"Lespiau, Damien" <damien.lespiau@intel.com>,
Ben Widawsky <bwidawsk@gmail.com>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
"Deak, Imre" <imre.deak@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"Kuoppala, Mika" <mika.kuoppala@intel.com>,
Matthew D Roper <matthew.d.roper@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
And
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm-intel split-up and new dim script
Date: Thu, 24 Nov 2016 13:24:27 +0200 [thread overview]
Message-ID: <87lgw9unmc.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uE48isoguc5jwQ3VjQk6jQzgttXpWtj0HAbOvoF7DYVzQ@mail.gmail.com>
On Thu, 24 Nov 2016, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> To get there you need to update dim and re-run the setup steps:
Perhaps needless to say, but please report any hickups you see
immediately on IRC and/or in reply to this mail!
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-24 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 10:48 drm-intel split-up and new dim script Daniel Vetter
2016-11-24 11:24 ` Jani Nikula [this message]
2016-11-24 15:06 ` Daniel Vetter
2016-12-01 8:11 ` 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=87lgw9unmc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=architt@codeaurora.org \
--cc=bwidawsk@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=hoegsberg@google.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=mika.kuoppala@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sumit.semwal@linaro.org \
--cc=treding@nvidia.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=ville.syrjala@linux.intel.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.