From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
Cc: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>,
"David Miller" <davem@davemloft.net>,
"Jeff Garzik" <jeff@garzik.org>, "Ingo Molnar" <mingo@elte.hu>,
"Bruce Allan" <bruce.w.allan@intel.com>,
netdev <netdev@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: skbuff bug?
Date: Tue, 26 Aug 2008 09:37:59 -0700 [thread overview]
Message-ID: <86802c440808260937y4a3e87dt4a897a05dc7fa7b@mail.gmail.com> (raw)
In-Reply-To: <9929d2390808260317l2fb17bcxe099e85fcf5bb939@mail.gmail.com>
On Tue, Aug 26, 2008 at 3:17 AM, Jeff Kirsher
<jeffrey.t.kirsher@intel.com> wrote:
> On Tue, Aug 26, 2008 at 2:17 AM, Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
>> Hi.
>>
>> On Thu, Aug 21, 2008 at 04:46:49PM -0700, Yinghai Lu (yhlu.kernel@gmail.com) wrote:
>>> it seems caused by
>>>
>>> commit f8d59f7826aa73c5e7682fbed6db38020635d466
>>> Author: Bruce Allan <bruce.w.allan@intel.com>
>>> Date: Fri Aug 8 18:36:11 2008 -0700
>>>
>>> e1000e: test for unusable MSI support
>>
>> Intel folks seems to be on vacations or whatever else without access to
>> the mail. Can you confirm that bug still exists in the latest tree and
>> reverting this commit fixes the problem?
>>
>> --
>> Evgeniy Polyakov
>> --
>
> We are looking into the issue, I am sorry there has been no response until now.
>
> I am still curious if you still see the issue with all the recent
> changes. Please provide the device id you are using and system info
> so that we can try and reproduce the issue, if the issue persists with
> the latest git tree.
can not duplicate any more...
YH
prev parent reply other threads:[~2008-08-26 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 3:56 Yinghai Lu
2008-08-21 23:46 ` Yinghai Lu
2008-08-22 1:23 ` Yinghai Lu
2008-08-26 9:17 ` Evgeniy Polyakov
2008-08-26 10:17 ` Jeff Kirsher
2008-08-26 16:37 ` Yinghai Lu [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=86802c440808260937y4a3e87dt4a897a05dc7fa7b@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@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
all inboxes | Powered by JetHome®