From: Craig <craig@haquarter.de>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Bugme-new] [Bug 16383] New: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
Date: Mon, 02 Aug 2010 23:23:36 +0200 [thread overview]
Message-ID: <4C573758.5040104@haquarter.de> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FFE8449AA@rrsmsx501.amr.corp.intel.com>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=16383
>>>
>>> Summary: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
>>> Product: Drivers
>>> Version: 2.5
>>> Kernel Version: 2.6.35
>>> Platform: All
>>> OS/Version: Linux
>>> Tree: Mainline
>>> Status: NEW
>>> Severity: high
>>> Priority: P1
>>> Component: Network
>>> AssignedTo: drivers_network@kernel-bugs.osdl.org
>>> ReportedBy: craig@haquarter.de
>>> Regression: Yes
>>>
>>>
>>> Networking stops working with 2.6.35 (tested rc-3 and rc5).
>>
>> This is a post-2.6.34 regression, guys. There's some more info in
>> bugzilla.
The e1000e works like a charm with 2.6.35, thanks everyone.
Best regards,
Craig
prev parent reply other threads:[~2010-08-02 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16383-10286@https.bugzilla.kernel.org/>
2010-07-21 20:48 ` [Bugme-new] [Bug 16383] New: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5 Andrew Morton
2010-07-21 21:43 ` Tantilov, Emil S
2010-07-22 0:06 ` Craig
2010-08-02 21:23 ` Craig [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=4C573758.5040104@haquarter.de \
--to=craig@haquarter.de \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=emil.s.tantilov@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/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.