From: Sam Ravnborg <sam@ravnborg.org>
To: dri-devel@lists.freedesktop.org
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@linux.ie>
Subject: Re: [PATCH v1 1/1] drm: fix alpha build after drm_util.h change
Date: Tue, 15 Jan 2019 07:03:54 +0100 [thread overview]
Message-ID: <20190115060354.GA28145@ravnborg.org> (raw)
In-Reply-To: <20190114180413.18117-1-sam@ravnborg.org>
Hi all.
Please do not apply.
O-DAY found a similar bug when building ia64, but this time there is
something else from irqflags.h that causes the error.
So...
> It was considered just to pull in interrupt.h but that would
> pull in a lot of unused stuff.
This seems to be the rigth solution anyway, as interrupt.h
have all the necessary dependencies.
I will try this tonight and post an updated patch.
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-01-15 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 18:04 [PATCH v1 1/1] drm: fix alpha build after drm_util.h change Sam Ravnborg
2019-01-15 6:03 ` Sam Ravnborg [this message]
2019-01-15 21:48 ` [PATCH v2 " Sam Ravnborg
2019-01-16 10:16 ` 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=20190115060354.GA28145@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=sean@poorly.run \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox