From: Jarod Wilson <jarod@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.sourceforge.net, xorg-devel@lists.x.org,
linux-kernel@vger.kernel.org, Florian Demmer <florian@demmer.org>,
eric@anholt.net
Subject: Re: [PATCH] drm: intel: add ignore lvds quirk info for AOpen Mini PC
Date: Mon, 1 Jun 2009 11:54:41 -0400 [thread overview]
Message-ID: <200906011154.42177.jarod@redhat.com> (raw)
In-Reply-To: <20090601120126.550b2d15@jbarnes-x200>
On Monday 01 June 2009 07:01:26 Jesse Barnes wrote:
> Patches to the i915 driver should generally go
> to intel-gfx@lists.freedesktop.org so we don't miss them. Thanks.
Ah, sorry, didn't know that. Might I suggest adding a note to that
effect in MAINTAINERS? Reasonably sure that's where I looked to try
to figure out where to send a prior i915 patch and I don't see a
ref to that list in there now.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-06-01 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 21:20 [PATCH] drm: intel: add ignore lvds quirk info for AOpen Mini PC Jarod Wilson
2009-06-01 11:01 ` Jesse Barnes
2009-06-01 15:54 ` Jarod Wilson [this message]
2009-06-01 16:11 ` Joe Perches
2009-06-01 16:17 ` Jesse Barnes
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=200906011154.42177.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=florian@demmer.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg-devel@lists.x.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