From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
To: "David Miller" <davem@davemloft.net>
Cc: linux.nics@intel.com, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, jaswinder@infradead.org
Subject: Re: [PATCH -net-next 1/4] firmware: convert e100 driver to request_firmware()
Date: Wed, 7 Jan 2009 10:23:44 -0800 [thread overview]
Message-ID: <9929d2390901071023s590f439fre15696786f098b81@mail.gmail.com> (raw)
In-Reply-To: <20090104.213402.12464178.davem@davemloft.net>
On Sun, Jan 4, 2009 at 9:34 PM, David Miller <davem@davemloft.net> wrote:
> From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
> Date: Sun, 4 Jan 2009 18:20:24 -0800
>
>> On Sun, Jan 4, 2009 at 4:06 PM, David Miller <davem@davemloft.net> wrote:
>> > From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
>> > Date: Tue, 30 Dec 2008 14:33:36 -0800
>> >
>> >> Please hold off on committing, until we have had ample time to do some
>> >> regression testing. While this patch may have been in linux-next,
>> >> this is the first we have seen of it.
>> >>
>> >> I am concerned that IPMI traffic will be adversely affected by this patch.
>> >
>> > Status please?
>> > --
>>
>> The only testing left to do is to make sure that ICH devices still
>> work and to make sure the IPMI traffic is not affected by this patch.
>> All other testing looks good. I am sorry that I have been slow to
>> give status, the holiday's have put a strain on available resources.
>
> Ok, thanks for the update.
> --
>
So here is the latest testing update...
The only testing that we were not able to do was the IPMI testing,
because of the lack of resources. All other testing passed.
While all other testing passed, I am concerned about not being able to
test whether or not this change affects the ability to pass IPMI
traffic. I am not sure if the "gain" of using request_firmware() out
weighs the potential risk that IPMI traffic may be broken with this
patch. I guess I wondering what the gain is in using the
request_firmware() function?
>From past experience with IPMI traffic and the e100, the loading of
the microcode in the correct manner greatly affected whether IPMI
traffic would pass or not.
--
Cheers,
Jeff
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
next prev parent reply other threads:[~2009-01-07 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 8:40 [PATCH -net-next 1/4] firmware: convert e100 driver to request_firmware() Jaswinder Singh Rajput
2008-12-30 22:33 ` Jeff Kirsher
2009-01-05 0:06 ` David Miller
2009-01-05 2:20 ` Jeff Kirsher
2009-01-05 5:34 ` David Miller
2009-01-07 18:23 ` Jeff Kirsher [this message]
2009-01-07 18:49 ` Jeff Kirsher
2009-01-07 20:39 ` David Miller
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=9929d2390901071023s590f439fre15696786f098b81@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux.nics@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).