From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/4] video: add fb_edid_add_monspecs for parsing extended edid information
Date: Thu, 28 Oct 2010 23:45:18 +0000 [thread overview]
Message-ID: <20101028234518.GB14720@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1010281427240.1257@axis700.grange>
On Thu, Oct 28, 2010 at 04:23:12PM -0700, Andrew Morton wrote:
> On Thu, 28 Oct 2010 14:34:44 +0200 (CEST)
> Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
>
> > From: Erik Gilling <konkers@android.com>
> >
> > Modern monitors/tvs have more extended EDID information blocks which can
> > contain extra detailed modes. This adds a fb_edid_add_monspecs function
> > which drivers can use to parse those additions blocks.
> >
> > Signed-off-by: Erik Gilling <konkers@android.com>
>
> This patch should also be signed-off-by:you, as you were on the
> delivery path.
>
> I hit a few rejects when merging agains current mainline, the
> drivers/video/sh_mobile_hdmi.c one was not completely trivial, so I ducked
> it all. Redo and resend, please.
>
There's also a bunch of stuff in the genesis tree heading to Linus via
rmk that will probably cause more headaches. Once that stuff has merged
then this patch will be much easier to apply.
next prev parent reply other threads:[~2010-10-28 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 12:34 [PATCH 1/4] video: add fb_edid_add_monspecs for parsing extended Guennadi Liakhovetski
2010-10-28 23:17 ` [PATCH 1/4] video: add fb_edid_add_monspecs for parsing Andrew Morton
2010-10-28 23:23 ` Andrew Morton
2010-10-28 23:45 ` Paul Mundt [this message]
2010-11-01 15:57 ` [PATCH 1/4] video: add fb_edid_add_monspecs for parsing extended Guennadi Liakhovetski
2010-11-01 17:42 ` [PATCH 1/4] video: add fb_edid_add_monspecs for parsing Andrew Morton
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=20101028234518.GB14720@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.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).