All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: [PATCH] drm-misc: arm64 now also must be compile-tested before pushing
Date: Tue, 23 Aug 2016 10:15:22 +0200	[thread overview]
Message-ID: <20160823081522.28704-1-daniel.vetter@ffwll.ch> (raw)

hisilicon unfortunately requires this since it's a warn-fest on 32bit
builds.

Cc: seanpaul@chromium.org
Cc: sumit.semwal@linaro.org
Cc: sumit.semwal@linaro.org
Cc: architt@codeaurora.org
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
 drm-misc.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drm-misc.rst b/drm-misc.rst
index 521be4aceceb..2f30e18d9095 100644
--- a/drm-misc.rst
+++ b/drm-misc.rst
@@ -26,8 +26,8 @@ Right now the only hard merge criteria are:
   in through separate pull requests. Those topic branches can still be
   maintained with the dim_ tooling, but that's of course entirely optional.
 
-* All the x86 and arm DRM drivers need to still compile. To simplify this we
-  track defconfigs for both platforms in the `drm-intel-rerere` branch.
+* All the x86, arm and arm64 DRM drivers need to still compile. To simplify this
+  we track defconfigs for all three platforms in the `drm-intel-rerere` branch.
 
 * The goal is to also pre-check everything with CI. Unfortunately neither the
   arm side (using kernelci.org and generic i-g-t tests) nor the Intel side
-- 
2.9.3

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2016-08-23  8:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160823081522.28704-1-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.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 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.