From: Florian Mickler <florian@mickler.org>
To: linux-kernel@vger.kernel.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: regression i915 / video driver
Date: Thu, 28 May 2009 20:48:44 +0200 [thread overview]
Message-ID: <20090528204844.58bf12d6@schatten> (raw)
In-Reply-To: <609771.46526.qm@web112217.mail.gq1.yahoo.com>
On Thu, 28 May 2009 09:44:23 -0700 (PDT)
We La <w.landgraf@yahoo.com> wrote:
>
> I inform that the problem with the i915 driver isnt yet resolved !!
>
> On the last kernel git's, at least on my ms wind 100 laptop, the
> video driver don't load correctly, and correspondingly the i915
> driver don't load at all, as explained before. With exactly the
> same system but booting with 2.6.29.4 (and all previous 2.6.29.X) the
> problem dont exist and everything works correctly.
>
> Werner LAndgraf
>
> SYS
>
Hi!
Do you have filled a bugzilla entry or have send previously messages to
this list?
It would be nice to include references to both such actions if they
took place. As there are quite a number of messages coming through this
list, it is likely, that your messages didn't get noticed before.
[i searched through lkml for your mailadress and found some messages,
which took me some time, but consider it a favour]:
http://lkml.org/lkml/2009/5/1/215
http://lkml.org/lkml/2009/4/30/731
Please file a bug at http://bugzilla.kernel.org/ and classify it as
a regression from 2.6.29. Also put all information available to you
about this bug in there.
This makes it easy to reference it.
The second step would be to assume that nobody noticed your messages
before and thus include all relevant information in each message,
making it easy for somebody reading it to understand what it is about.
(if you just have to quote a bugzilla bug number, of course, that's
easy)
The third step would probably be, to find someone to talk to. An email
about i915 is likely to get more attention on
intel-gfx@lists.freedesktop.org
And it would be kind of you to read
http://www.kernel.org/pub/linux/docs/lkml/ . (spcifically the
mailinglist 'rules'... )
out of respect to others, so that they (I?) don't have to do
unnecessary work.
Especially:
1. If you are replying to a specific mail, plz include the relevant part
of it you are replying to and
2. use your mail-clients reply-to-all button, so that the mail get's
linked to the mail you are replying to.
Sincerely,
Florian
prev parent reply other threads:[~2009-05-28 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 16:44 regression i915 / video driver We La
2009-05-28 18:48 ` Florian Mickler [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=20090528204844.58bf12d6@schatten \
--to=florian@mickler.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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