netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eliezer Tamir" <eliezert@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: jeff@garzik.org, netdev@vger.kernel.org, mchan@broadcom.com
Subject: Re: [PATCH 1/8][BNX2X] resubmit as attachments: add bnx2x to Kconfig and Makefile
Date: Tue, 09 Oct 2007 06:13:23 +0200	[thread overview]
Message-ID: <470AFFE3.100@broadcom.com> (raw)
In-Reply-To: <20071008.174603.55855492.davem@davemloft.net>

David Miller wrote:
> From: "Eliezer Tamir" <eliezert@broadcom.com>
> Date: Mon, 08 Oct 2007 18:15:17 +0200
> 
>> Add bnx2x to Kconfig and Makefile
> 
> In a patch submission, the tree should build on every step along the
> way in applying your patches, with any given configuration.
> 
> Here, the user (or something automated like "make allmodconfig") can
> select the new config option, but because the driver source hasn't
> been added, the compile will fail.
> 
> The idea is that if your patch set really is composed of logically
> seperate changes, you submit them one logical compilable piece at a
> time, and if the first few patches are ok, they could go right in
> whilst we work out issues in later patches.  But that's not how
> a new driver is, it is logically one change only.
> 
> You go on next to add a foo.c file, and then a foo.h file.
> This makes things even more difficult to review.
> 
> Really, for a new driver that doesn't make any generic kernel code
> changes, just submit the whole thing in one shot.  It's the only
> reasonable way.
> 
> Thank you.
> 

Due to the size of the patch I can not post it to the list.

Here is an FTP link.
ftp://Net_sys_anon@ftp1.broadcom.com/bnx2x-0.40.10-net-2.6.24-one.patch.txt

Or if you prefer, I can post it gzipped.

Thanks
Eliezer



  reply	other threads:[~2007-10-09  4:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 16:15 [PATCH 1/8][BNX2X] resubmit as attachments: add bnx2x to Kconfig and Makefile Eliezer Tamir
2007-10-09  0:46 ` David Miller
2007-10-09  4:13   ` Eliezer Tamir [this message]
2007-10-09  4:29     ` David Miller
2007-10-09 16:20       ` Eliezer Tamir
2007-10-10  9:34         ` 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=470AFFE3.100@broadcom.com \
    --to=eliezert@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=mchan@broadcom.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).