From: Keith Packard <keithp@keithp.com>
To: Eugeni Dodonov <eugeni@dodonov.net>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
Eugeni Dodonov <eugeni.dodonov@intel.com>
Subject: Re: [PATCH 1/2] drm: give up on edid retries when i2c bus is not responding
Date: Thu, 05 Jan 2012 07:50:57 -0800 [thread overview]
Message-ID: <86vcoq87xa.fsf@sumi.keithp.com> (raw)
In-Reply-To: <CAC7Lmnv3UChEqfSNZEayjjeCC-RRGeQf3AmgAH=BA+N7tifkqA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]
On Thu, 5 Jan 2012 13:37:50 -0200, Eugeni Dodonov <eugeni@dodonov.net> wrote:
> I'd be happy to include it into any kernel out there, 3.4 would be fine. I
> originally sent it for 3.1 merge though, and so far it haven't been picked
> up by any tree. So I am a bit lost about what to do with this next, besides
> re-sending the same patch over and over again...
I'll stick it in drm-intel-next, once Dave pulls for 3.3.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-01-05 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 11:34 [PATCH 1/2] drm: give up on edid retries when i2c bus is not responding Eugeni Dodonov
2012-01-05 11:34 ` [PATCH 2/2] drm/i915: there is no pipe CxSR on ironlake Eugeni Dodonov
2012-01-16 20:30 ` Daniel Vetter
2012-01-05 14:43 ` [PATCH 1/2] drm: give up on edid retries when i2c bus is not responding Daniel Vetter
2012-01-05 15:37 ` Eugeni Dodonov
2012-01-05 15:50 ` Keith Packard [this message]
2012-01-16 20:33 ` [Intel-gfx] " Daniel Vetter
2012-01-20 20:06 ` Fwd: " Eugeni Dodonov
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=86vcoq87xa.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=daniel@ffwll.ch \
--cc=eugeni.dodonov@intel.com \
--cc=eugeni@dodonov.net \
--cc=intel-gfx@lists.freedesktop.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.