From: rmk@arm.linux.org.uk (Russell King)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] TDA998x fixes
Date: Sat, 5 Jul 2014 11:57:42 +0100 [thread overview]
Message-ID: <20140705105742.GA1811@rmk-PC.arm.linux.org.uk> (raw)
David,
Please incorporate the latest TDA998x fixes, which can be found at:
git://ftp.arm.linux.org.uk/~rmk/linux-cubox.git tda998x-fixes
with SHA1 de4bf3d51fe38eaf90cb587e4eae1f3f0e056a54.
A number of relatively minor TDA998x fixes, the most serious of which
is the positioning of the drm_i2c_encoder_destroy call, which is marked
for inclusion in stable trees.
These changes are based on v3.15, and test merging with your drm-fixes
(0fcb70c30131) dated 27th June shows no conflicts.
This will update the following files:
Documentation/devicetree/bindings/drm/i2c/tda998x.txt | 2 ++
drivers/gpu/drm/i2c/tda998x_drv.c | 12 +++++++++---
2 files changed, 11 insertions(+), 3 deletions(-)
through these changes:
Guido Mart?nez (1):
drm/i2c: tda998x: move drm_i2c_encoder_destroy call
Jean-Francois Moine (1):
drm/i2c: tda998x: fix lack of required reg in DT documentation
Russell King (2):
drm/i2c: tda998x: faster polling for edid
drm/i2c: tda998x: add some basic mode validation
Many thanks.
reply other threads:[~2014-07-05 10:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140705105742.GA1811@rmk-PC.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).