From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: jaswinder@infradead.org, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH -net-next 1/4] firmware: convert e100 driver to request_firmware()
Date: Wed, 07 Jan 2009 12:39:54 -0800 (PST) [thread overview]
Message-ID: <20090107.123954.257436361.davem@davemloft.net> (raw)
In-Reply-To: <9929d2390901071023s590f439fre15696786f098b81@mail.gmail.com>
From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
Date: Wed, 7 Jan 2009 10:23:44 -0800
> 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.
Jeff, I've lost all of my patience.
All drivers are being converted this way. I fought against doing it
to tg3 for various reasons, but the tide worked against me and I
accepted that.
We can't hold this patch up forever for a potential problem that you
don't have the resources to even test for more than a week.
I'm therefore adding this patch, and we'll fix or revert if the
"possible" IPMI problems do surface.
prev parent reply other threads:[~2009-01-07 20:39 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
2009-01-07 18:49 ` Jeff Kirsher
2009-01-07 20:39 ` David Miller [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=20090107.123954.257436361.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jaswinder@infradead.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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