From: Sam Ravnborg <sam@ravnborg.org>
To: Inki Dae <daeinki@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Jingoo Han <jingoohan1@gmail.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Kukjin Kim <kgene@kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v4 2/2] drm/exynos: trigger build of all modules
Date: Mon, 24 Jun 2019 17:29:44 +0200 [thread overview]
Message-ID: <20190624152944.GA20945@ravnborg.org> (raw)
In-Reply-To: <CAAQKjZPqunjVctjFJdwJMEmz7DHT8mDgMQ-_a3sw6BGO9K2q2w@mail.gmail.com>
Hi Inki
From changelog:
> >
> > Include fix of exynos build for alpha.
> >
> > diff --git a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
> > index aefcd624fe32..b0877b97291c 100644
> > --- a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
> > +++ b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
> > @@ -10,6 +10,7 @@
> >
> > #include <linux/console.h>
> > #include <linux/dma-mapping.h>
> > +#include <linux/vmalloc.h>
>
> Is this change related to this patch?
This is the above mentioned fix.
Alpha often needs one to pull in vmalloc.h - where all other
architectures get it indirect via other headers.
I have never bothered to find out why alpa needs more headers files,
but I always make sure to test things using alpha so 0-day do not yell at me.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-24 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 11:56 [PATCH v4 0/2] drm/exynos: drop use of drmP.h Sam Ravnborg
2019-06-22 11:56 ` [PATCH v4 1/2] drm/exynos: drop drmP.h usage Sam Ravnborg
2019-06-24 13:32 ` Inki Dae
2019-06-24 13:34 ` Inki Dae
2019-06-22 11:56 ` [PATCH v4 2/2] drm/exynos: trigger build of all modules Sam Ravnborg
2019-06-24 13:47 ` Inki Dae
2019-06-24 15:29 ` Sam Ravnborg [this message]
2019-06-25 12:48 ` Inki Dae
2019-06-25 4:59 ` Sam Ravnborg
2019-06-26 15:54 ` Inki Dae
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=20190624152944.GA20945@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=daeinki@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=sw0312.kim@samsung.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.