All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the omap_dss2 tree
Date: Wed, 5 Mar 2014 09:01:54 +0200	[thread overview]
Message-ID: <5316CBE2.2020302@ti.com> (raw)
In-Reply-To: <20140305143219.1613f7dcad9ab8a3290be9ee@canb.auug.org.au>

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

On 05/03/14 05:32, Stephen Rothwell wrote:
> Hi Tomi,
> 
> After merging the omap_dss2 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/video/fbdev/aty/mach64_cursor.c:8:24: fatal error: ../fb_draw.h: No such file or directory
>  #include "../fb_draw.h"
>                         ^
> 
> Caused by commit 236c52f2ad52 ("fbdev: move fbdev core files to separate directory").
> 
> I have used the omap_dss2 tree from next-20140304 for today.

Thanks. It was a bad merge between the main fbdev changes and the fbdev
restructuring. I've fixed it and pushed the branch.

 Tomi



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

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the omap_dss2 tree
Date: Wed, 5 Mar 2014 09:01:54 +0200	[thread overview]
Message-ID: <5316CBE2.2020302@ti.com> (raw)
In-Reply-To: <20140305143219.1613f7dcad9ab8a3290be9ee@canb.auug.org.au>

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

On 05/03/14 05:32, Stephen Rothwell wrote:
> Hi Tomi,
> 
> After merging the omap_dss2 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/video/fbdev/aty/mach64_cursor.c:8:24: fatal error: ../fb_draw.h: No such file or directory
>  #include "../fb_draw.h"
>                         ^
> 
> Caused by commit 236c52f2ad52 ("fbdev: move fbdev core files to separate directory").
> 
> I have used the omap_dss2 tree from next-20140304 for today.

Thanks. It was a bad merge between the main fbdev changes and the fbdev
restructuring. I've fixed it and pushed the branch.

 Tomi



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

  reply	other threads:[~2014-03-05  7:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  3:32 linux-next: build failure after merge of the omap_dss2 tree Stephen Rothwell
2014-03-05  7:01 ` Tomi Valkeinen [this message]
2014-03-05  7:01   ` Tomi Valkeinen
  -- strict thread matches above, loose matches on Subject: below --
2014-11-17  8:09 Stephen Rothwell
2014-11-18 14:53 ` Tomi Valkeinen
2014-11-18 14:53   ` Tomi Valkeinen
2014-11-18 15:07   ` David Herrmann
2014-11-25 11:00     ` Tomi Valkeinen
2014-11-25 11:20       ` Hans de Goede
2014-11-25 12:11         ` Tomi Valkeinen
2014-11-25 22:07           ` Stephen Rothwell
2014-11-26  8:16             ` Tomi Valkeinen
2014-03-04  3:35 Stephen Rothwell
2014-03-04  6:58 ` Tomi Valkeinen
2014-03-04  6:58   ` Tomi Valkeinen
2013-04-26  5:10 Stephen Rothwell
2013-04-26  5:31 ` Tomi Valkeinen
2013-04-26  5:31   ` Tomi Valkeinen
2013-04-26  5:56   ` Stephen Rothwell
2013-04-26  5:56     ` Stephen Rothwell
2013-04-26  6:57     ` Tomi Valkeinen
2013-04-26  6:57       ` Tomi Valkeinen

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=5316CBE2.2020302@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.