public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp•com>
To: Michael Chan <mchan@broadcom•com>
Cc: Bastian Blank <waldi@debian•org>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [PATCH] bnx2: Use request_firmware()
Date: Mon, 23 Mar 2009 17:14:36 -0700	[thread overview]
Message-ID: <49C825EC.50100@hp.com> (raw)
In-Reply-To: <1237850656.18617.34.camel@HP1>

Michael Chan wrote:
> May be I'll break up each firmware section into a
> different file and the file name will be updated with each version.
> This will allow different sections to be updated separately and older
> kernels will still have access to the older firmware.

Is that really necessary?  It is enough "fun" finding just the one firmware file 
as it is.

rick jones

  reply	other threads:[~2009-03-24  0:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 22:29 [PATCH] bnx2: Use request_firmware() Ben Hutchings
2009-03-19 23:04 ` Michael Chan
2009-03-19 23:25   ` Bastian Blank
2009-03-20 22:50     ` David Miller
2009-03-23 21:47       ` Michael Chan
2009-03-23 22:02         ` David Miller
2009-03-23 22:29         ` Bastian Blank
2009-03-23 23:24           ` Michael Chan
2009-03-24  0:14             ` Rick Jones [this message]
2009-03-24  1:11               ` Michael Chan
2009-03-24  1:26                 ` Rick Jones
2009-03-24  1:44                   ` Michael Chan
2009-03-24  4:27                   ` Ben Hutchings
2009-03-24  7:42                 ` Bastian Blank
2009-03-24 15:27                   ` Michael Chan
2009-03-23 22:32         ` Bastian Blank
2009-03-23 23:28           ` Michael Chan
2009-04-01 18:01             ` Michael Chan
2009-04-02  8:05               ` David Miller
     [not found] <1238778120-8132-1-git-send-email-mchan@broadcom.com>
2009-04-04 23:51 ` 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=49C825EC.50100@hp.com \
    --to=rick.jones2@hp$(echo .)com \
    --cc=mchan@broadcom$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=waldi@debian$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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