From: Pavel Machek <pavel@ucw.cz>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [GIT PULL] fbdev fixes for 3.19
Date: Sat, 20 Dec 2014 21:01:25 +0000 [thread overview]
Message-ID: <20141220210125.GB16705@amd> (raw)
In-Reply-To: <54899F0E.4090309@ti.com>
Hi!
> Please pull fbdev changes for 3.19.
>
> Tomi
v3.19-rc0 breaks video on my n900.
> Archit Taneja (7):
> OMAPDSS: DPI: Use DPI driver data
> OMAPDSS: DPI: Allocate driver data
> OMAPDSS: DPI: Store dpi_data pointer in the DT port's data
> OMAPDSS: DSS: init dss ports cleanly
> OMAPDSS: DT: Get source endpoint by matching reg-id
> OMAPDSS: DPI: Add support for multiple instances
> OMAPDSS: DSS: add a param to dpi_select_source which specifies
> it's port number
And I have these in my tree, so I should have latest fixes. Any ideas
what I should try?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [GIT PULL] fbdev fixes for 3.19
Date: Sat, 20 Dec 2014 22:01:25 +0100 [thread overview]
Message-ID: <20141220210125.GB16705@amd> (raw)
In-Reply-To: <54899F0E.4090309@ti.com>
Hi!
> Please pull fbdev changes for 3.19.
>
> Tomi
v3.19-rc0 breaks video on my n900.
> Archit Taneja (7):
> OMAPDSS: DPI: Use DPI driver data
> OMAPDSS: DPI: Allocate driver data
> OMAPDSS: DPI: Store dpi_data pointer in the DT port's data
> OMAPDSS: DSS: init dss ports cleanly
> OMAPDSS: DT: Get source endpoint by matching reg-id
> OMAPDSS: DPI: Add support for multiple instances
> OMAPDSS: DSS: add a param to dpi_select_source which specifies
> it's port number
And I have these in my tree, so I should have latest fixes. Any ideas
what I should try?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-12-20 21:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:41 [GIT PULL] fbdev fixes for 3.19 Tomi Valkeinen
2014-12-11 13:41 ` Tomi Valkeinen
2014-12-11 20:55 ` Linus Torvalds
2014-12-11 20:55 ` Linus Torvalds
2014-12-11 22:58 ` Rafael J. Wysocki
2014-12-11 22:58 ` Rafael J. Wysocki
2014-12-12 0:59 ` Rob Herring
2014-12-12 0:59 ` Rob Herring
2014-12-12 15:25 ` Rafael J. Wysocki
2014-12-12 15:25 ` Rafael J. Wysocki
2014-12-20 21:01 ` Pavel Machek [this message]
2014-12-20 21:01 ` Pavel Machek
2014-12-20 21:20 ` Pavel Machek
2014-12-20 21:20 ` Pavel Machek
2014-12-20 21:57 ` Pavel Machek
2014-12-20 21:57 ` Pavel Machek
2014-12-23 11:12 ` Pavel Machek
2014-12-23 11:12 ` Pavel Machek
2014-12-29 8:13 ` Tomi Valkeinen
2014-12-29 8:13 ` Tomi Valkeinen
2014-12-30 11:44 ` Tomi Valkeinen
2014-12-30 11:44 ` Tomi Valkeinen
2015-01-15 11:23 ` Tomi Valkeinen
2015-01-15 11:23 ` 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=20141220210125.GB16705@amd \
--to=pavel@ucw.cz \
--cc=broonie@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=torvalds@linux-foundation.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 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.