From: Paul Mundt <lethal@linux-sh.org>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: "linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
ext Tony Lindgren <tony@atomide.com>
Subject: Re: [GIT PULL] OMAP DSS changes for .38 merge window v2
Date: Tue, 11 Jan 2011 12:00:40 +0900 [thread overview]
Message-ID: <20110111030040.GF3760@linux-sh.org> (raw)
In-Reply-To: <1294653062.2529.28.camel@tubuntu>
On Mon, Jan 10, 2011 at 11:51:02AM +0200, Tomi Valkeinen wrote:
> Here's a new pull request for OMAP display subsystem patches. This one
> is rebased on top of the new omap patches on mainline, and the resulting
> board file conflict has been fixed.
>
> And while rebasing, I squashed the topmost patch, OMAP: DSS2: Fix build
> breaks for rfbi.c and dsi.c, into the respective patches. The patch
> contained only a few trivial compile fixes to errors which mistakenly
> slipped in.
>
Pulled, thanks.
prev parent reply other threads:[~2011-01-11 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 9:51 [GIT PULL] OMAP DSS changes for .38 merge window v2 Tomi Valkeinen
2011-01-11 3:00 ` Paul Mundt [this message]
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=20110111030040.GF3760@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox