From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Andrew Morton <akpm@linux-foundation.org>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
"tony@atomide.com" <tony@atomide.com>,
"hvaibhav@ti.com" <hvaibhav@ti.com>,
"khasim@ti.com" <khasim@ti.com>,
"sakoman@gmail.com" <sakoman@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/18] OMAP: DSS2: Intro
Date: Thu, 17 Sep 2009 10:13:22 +0300 [thread overview]
Message-ID: <1253171604.5927.17.camel@tubuntu> (raw)
In-Reply-To: <20090902151126.f465bb15.akpm@linux-foundation.org>
Hi,
On Thu, 2009-09-03 at 00:11 +0200, ext Andrew Morton wrote:
> On Tue, 01 Sep 2009 10:10:19 +0300
> Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> > Andrew,
> >
> > could you please help with merging this piece of (well written) code?
> > Could you give your blessing to include it into linux-next now, and
> > merge this during the next merge window?
>
> I'll merge them (after I've looked through them, which I'll do now).
Have you had time to take a look at this?
Tomi
>
> But there are more rejects than I'm prepared to cope with. The various
> arch/arm files have undergone some changes in linux-next which yield
> more breakage than I'm prepared to try to fix. For example,
> arch/arm/mach-omap2/board-3430sdp.c:sdp3430_config[] ends up being an
> empty array!
>
> Then there's the matter of these patches, already in -mm:
>
> omapfb-add-support-for-the-apollon-lcd.patch
> omapfb-add-support-for-mipi-dcs-compatible-lcds.patch
> omapfb-add-support-for-the-amstrad-delta-lcd.patch
> omapfb-add-support-for-the-2430sdp-lcd.patch
> omapfb-add-support-for-the-omap2evm-lcd.patch
> omapfb-add-support-for-the-3430sdp-lcd.patch
> omapfb-add-support-for-the-omap3-evm-lcd.patch
> omapfb-add-support-for-the-omap3-beagle-dvi-output.patch
> omapfb-add-support-for-the-gumstix-overo-lcd.patch
> omapfb-add-support-for-the-zoom-mdk-lcd.patch
> omapfb-add-support-for-rotation-on-the-blizzard-lcd-ctrl.patch
> n770-enable-lcd-mipi-dcs-in-kconfig.patch
> omapfb-dispc-various-typo-fixes.patch
> omapfb-dispc-disable-iface-clocks-along-with-func-clocks.patch
> omapfb-dispc-enable-wake-up-capability.patch
> omapfb-dispc-allow-multiple-external-irq-handlers.patch
> omapfb-suspend-resume-only-if-fb-device-is-already-initialized.patch
> omapfb-fix-coding-style-remove-dead-line.patch
> omapfb-add-fb-manual-update-option-to-kconfig.patch
> omapfb-hwa742-fix-pointer-to-be-const.patch
>
prev parent reply other threads:[~2009-09-17 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251462337-12531-1-git-send-email-tomi.valkeinen@nokia.com>
2009-08-31 9:23 ` [PATCH 00/18] OMAP: DSS2: Intro Artem Bityutskiy
2009-08-31 13:54 ` Koen Kooi
2009-08-31 14:20 ` Steve Sakoman
2009-08-31 14:40 ` Syed Mohammed, Khasim
[not found] ` <0680EC522D0CC943BC586913CF3768C0037CE48136@dbde02.ent.ti.com>
2009-08-31 14:44 ` Hiremath, Vaibhav
2009-08-31 15:55 ` Tony Lindgren
2009-09-01 7:10 ` Artem Bityutskiy
2009-09-01 16:08 ` Tony Lindgren
2009-09-02 22:11 ` Andrew Morton
2009-09-03 11:00 ` Tomi Valkeinen
2009-09-10 18:44 ` Hiremath, Vaibhav
2009-09-17 7:13 ` Tomi Valkeinen [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=1253171604.5927.17.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--cc=hvaibhav@ti.com \
--cc=khasim@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.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