From: Tony Lindgren <tony@atomide.com>
To: Cory Maccarrone <darkstar6262@gmail.com>,
Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: Belisko Marek <marek.belisko@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] Fix include problem. Signed-off-by: Marek Belisko <marek.belisko@gmail.com>
Date: Fri, 4 Dec 2009 15:00:12 -0800 [thread overview]
Message-ID: <20091204230012.GN24013@atomide.com> (raw)
In-Reply-To: <6cb013310912030729k2b42e2edqfe7a63f9c046bb89@mail.gmail.com>
* Cory Maccarrone <darkstar6262@gmail.com> [091203 07:28]:
> On Thu, Dec 3, 2009 at 5:28 AM, Belisko Marek <marek.belisko@gmail.com> wrote:
> >
> > Hi,
> >
> > when make htcherald_defconfig on current linux-omap tree
> > (82f1d8f22f2c65e70206e40a6f17688bf64a892c) compilation fails
> > in drivers/video/omap/lcd_htcherald.c.
> >
> > Following patch fixed this problem.
>
> Marek and I talked on IRC about this, and it turns out this is true on
> the linux-omap master branch, but for-next compiles without issue,
> possibly due to the header changes not having been done on the master
> branch yet.
Looks like Tomi's DSS2 moved this around. The DSS2 code is merged
into linux-omap master branch, but is not in omap for-next branch.
I've applied this to linux-omap master branch for now.
Tomi, can you please add this to your fixes queue?
The patch in question is at:
http://patchwork.kernel.org/patch/64520/
Regards,
Tony
next prev parent reply other threads:[~2009-12-04 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 13:28 [PATCH] Fix include problem. Signed-off-by: Marek Belisko <marek.belisko@gmail.com> Belisko Marek
2009-12-03 15:29 ` Cory Maccarrone
2009-12-04 23:00 ` Tony Lindgren [this message]
2009-12-07 9:11 ` Tomi Valkeinen
2009-12-04 22:57 ` [APPLIED] [PATCH] Fix include problem. Signed-off-by: Marek Belisko Tony Lindgren
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=20091204230012.GN24013@atomide.com \
--to=tony@atomide.com \
--cc=darkstar6262@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=tomi.valkeinen@nokia.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.