public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"James Qian Wang (Arm Technology China)"
	<james.qian.wang@arm.com>
Subject: linux-next: build failure after merge of the mali-dp tree
Date: Mon, 14 Jan 2019 12:21:38 +1100	[thread overview]
Message-ID: <20190114122138.724ba326@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

Hi all,

After merging the mali-dp tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from drivers/gpu/drm/arm/display/komeda/komeda_framebuffer.c:11:
drivers/gpu/drm/arm/display/komeda/komeda_framebuffer.h:13:25: error: field 'base' has incomplete type
  struct drm_framebuffer base;
                         ^~~~

Caused by commit

  31849148cb41 ("drm/komeda: Add komeda_framebuffer")

I have used the mali-dp tree from next-20190111 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-01-14  1:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  1:21 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-14 23:46 linux-next: build failure after merge of the mali-dp tree Stephen Rothwell
2019-01-15 10:12 ` Liviu Dudau
2019-01-15 10:47   ` Stephen Rothwell
2019-01-15 10:51     ` Liviu Dudau
2019-01-15 12:08       ` Daniel Vetter
2019-01-15 12:23         ` Liviu Dudau
2019-01-15 13:37           ` 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=20190114122138.724ba326@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Liviu.Dudau@arm.com \
    --cc=james.qian.wang@arm.com \
    --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