From: Jeff Garzik <jgarzik@pobox.com>
To: Ajit Khaparde <ajitk@serverengines.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [RFC][PATCH][v5] net/ethtool: Add support for the ethtool feature to flash firmware image from a specified file.
Date: Wed, 02 Sep 2009 12:48:23 -0400 [thread overview]
Message-ID: <4A9EA1D7.8090002@pobox.com> (raw)
In-Reply-To: <20090902162241.GB23228@serverengines.com>
On 09/02/2009 12:22 PM, Ajit Khaparde wrote:
> On 21/08/09 22:24 +0530, Ajit Khaparde wrote:
>> This patch adds support to flash a firmware image to a device using ethtool.
>> The driver gets the filename of the firmware image and flashes the image
>> using the request firmware path.
>>
>> The region "on the chip" to be flashed can be specified by an option.
>> It is upto the device driver to enumerate the region number passed by ethtool,
>> to the region to be flashed.
>>
>> The default behavior is to flash all the regions on the chip.
> David,
> Is this patch good enough for being accepted? Please let me know if any more
> work has to be done on this.
>
> I want to send the changes to the be2net driver which would use this
> new ethtool feature. Any ETA for applying the patch to the git tree?
> I will schedule my driver patch according to that.
BTW, don't forget to update the ethtool userland utility as well,
git://git.kernel.org/pub/scm/network/ethtool/ethtool.git
Jeff
next prev parent reply other threads:[~2009-09-02 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 16:54 [RFC][PATCH][v5] net/ethtool: Add support for the ethtool feature to flash firmware image from a specified file Ajit Khaparde
2009-09-02 15:50 ` Ajit Khaparde
2009-09-02 21:40 ` David Miller
2009-09-03 3:02 ` Ajit Khaparde
2009-09-02 16:22 ` Ajit Khaparde
2009-09-02 16:48 ` Jeff Garzik [this message]
2009-09-02 17:00 ` Ben Hutchings
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=4A9EA1D7.8090002@pobox.com \
--to=jgarzik@pobox.com \
--cc=ajitk@serverengines.com \
--cc=davem@davemloft.net \
--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).