From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Brian Starkey <brian.starkey@arm.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Liviu Dudau <Liviu.Dudau@arm.com>,
linux-arm-kernel@lists.infradead.org, Jyri Sarha <jsarha@ti.com>
Subject: Re: [PATCH 1/2] drm/i2c: tda998x: allow interrupt to be shared
Date: Thu, 17 Nov 2016 16:38:02 +0000 [thread overview]
Message-ID: <20161117163801.GG1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20161117122457.GC21156@e106950-lin.cambridge.arm.com>
On Thu, Nov 17, 2016 at 12:24:57PM +0000, Brian Starkey wrote:
> I tested these two and the power-down one on mali-dp and hdlcd. The
> output, hotplugging and EDID continued to work; so you can have my
> tested-by and reviewed-by for all 3.
Thanks!
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2016-11-17 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 10:48 [PATCH 1/2] drm/i2c: tda998x: allow interrupt to be shared Russell King
2016-11-17 12:24 ` Brian Starkey
2016-11-17 16:38 ` Russell King - ARM Linux [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=20161117163801.GG1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@linux.ie \
--cc=brian.starkey@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--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).