linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Sep 19 (amdgpu)
Date: Thu, 19 Sep 2019 12:28:26 -0700	[thread overview]
Message-ID: <0323499e-9fbd-a707-9713-cb40cc92b6fc@infradead.org> (raw)
In-Reply-To: <20190919160641.GR3642@sirena.co.uk>

On 9/19/19 9:06 AM, Mark Brown wrote:
> Hi all,
> 
> Changes since 20190918:
> 


../drivers/gpu/drm/amd/amdgpu/../display/dc/dml/Makefile:70: *** missing 'endif'.  Stop.


-- 
~Randy

  reply	other threads:[~2019-09-19 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 16:06 linux-next: Tree for Sep 19 Mark Brown
2019-09-19 19:28 ` Randy Dunlap [this message]
2019-09-20 11:17 ` [next-20190919] Build failure: undefined "hash__has_transparent_hugepage Sachin Sant

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=0323499e-9fbd-a707-9713-cb40cc92b6fc@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).