public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jesse.brandeburg@intel.com
Subject: Re: Linux 2.6.27-rc8
Date: Tue, 30 Sep 2008 16:09:50 +0200	[thread overview]
Message-ID: <m3d4ilk9n5.fsf@maximus.localdomain> (raw)
In-Reply-To: <alpine.LNX.1.10.0809300859590.4022@jikos.suse.cz> (Jiri Kosina's message of "Tue\, 30 Sep 2008 09\:06\:33 +0200 \(CEST\)")

Jiri Kosina <jkosina@suse.cz> writes:

> So far it seems to be that you need 1) something close to xorg 7.4 and 
> 2) 2.6.27-rcX kernel to trigger it. Not every system having e1000e is 
> affected.

And this e1000e must be ICH*, right? I.e. not a separate e1000e
chip/card?
-- 
Krzysztof Halasa

  reply	other threads:[~2008-09-30 14:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 22:39 Linux 2.6.27-rc8 Linus Torvalds
2008-09-29 23:09 ` david
2008-09-29 23:33 ` Jiri Kosina
2008-09-30  1:56   ` Linus Torvalds
2008-09-30  1:59     ` Dave Airlie
2008-09-30  2:06       ` Arjan van de Ven
2008-09-30  2:23         ` Linus Torvalds
2008-09-30  2:24           ` Linus Torvalds
2008-09-30 12:06             ` Alan Cox
2008-09-30  3:42           ` Brandeburg, Jesse
2008-09-30 12:05           ` Alan Cox
2008-09-30  2:21       ` Linus Torvalds
2008-09-30  2:39         ` Dave Airlie
2008-09-30  3:19         ` Arjan van de Ven
2008-09-30  7:11         ` Jiri Kosina
2008-09-30  7:58           ` Eric Piel
2008-09-30 16:28             ` Luiz Fernando N. Capitulino
2008-09-30 18:27               ` Herton Ronaldo Krzesinski
2008-09-30  2:30     ` Brandeburg, Jesse
2008-09-30 22:07       ` Thomas Gleixner
2008-09-30  7:06     ` Jiri Kosina
2008-09-30 14:09       ` Krzysztof Halasa [this message]
2008-09-30 14:11         ` Jiri Kosina
2008-09-30 15:48           ` Allan, Bruce W
2008-10-01 15:37             ` Jiri Kosina
2008-09-30  7:43 ` Typo bug [Re: Linux 2.6.27-rc8] J.A. Magallón
2008-09-30  7:55   ` Ingo Molnar
2008-09-30  8:02     ` J.A. Magallón
2008-09-30  8:05       ` Ingo Molnar
2008-10-01 21:33         ` Domenico Andreoli
2008-10-02  5:27           ` Willy Tarreau
2008-10-02  9:26             ` Ingo Molnar
2008-10-02  9:45               ` Domenico Andreoli
2008-09-30 18:47     ` H. Peter Anvin
2008-09-30 19:30       ` Yinghai Lu
2008-09-30 19:59         ` H. Peter Anvin
2008-09-30 21:35           ` Yinghai Lu
2008-09-30 21:37             ` H. Peter Anvin
2008-09-30 21:42               ` Yinghai Lu
2008-09-30 22:02                 ` H. Peter Anvin

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=m3d4ilk9n5.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=jesse.brandeburg@intel.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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