netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>
Cc: <netdev@oss.sgi.com>, <leonid.grossman@s2io.com>,
	<raghavendra.koushik@s2io.com>, <rapuru.sriram@s2io.com>
Subject: RE: Patch submission for S2io Xframe driver to 2.6 kernel
Date: Tue, 28 Sep 2004 10:13:48 -0700	[thread overview]
Message-ID: <002b01c4a57e$84da0700$a010100a@S2IOtech.com> (raw)
In-Reply-To: <41597DA4.5040200@pobox.com>

Hi Jeff, Randy,
We are sorry about that. We will split the first patch into multiple smaller
patches and resubmit them one-by-one.
We appreciate all your patience.

Regards,
Ravi

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Tuesday, September 28, 2004 8:05 AM
To: ravinandan.arakali@s2io.com
Cc: netdev@oss.sgi.com; leonid.grossman@s2io.com;
raghavendra.koushik@s2io.com; rapuru.sriram@s2io.com
Subject: Re: Patch submission for S2io Xframe driver to 2.6 kernel


Ravinandan Arakali wrote:
> Hi,
> Attached are the updated patches. It is designed to work on the latest
> kernel. Also, this time the submission is split to 3 patches(they need
> to applied in the order mentioned below).
>
> s2io_styling_level1  - Contains
>                              a. styling related, function name changes.
>                              b. fix for 32-bit systems.
>                              c. modified Transmit descriptor allocation
> strategy.
>                              d. miscellaneous fixes.


When we say "separate logical changes", we mean it :)

This means that your level1 patch should be split into at least 4 patches.

Second, send each patch in a separate email, as described in
http://linux.yyz.us/patch-format.html (and
Documentation/SubmittingPatches) rather than sending as a tarball.

	Jeff

  reply	other threads:[~2004-09-28 17:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14  0:19 Patch submission for S2io Xframe driver to 2.6 kernel Ravinandan Arakali
2004-08-14  4:27 ` TCP hardware assists Leonid Grossman
2004-08-21  6:21 ` Patch submission for S2io Xframe driver to 2.6 kernel Randy.Dunlap
2004-08-21 23:43 ` Francois Romieu
2004-08-28 23:36 ` Jeff Garzik
2004-08-29  5:53   ` Leonid Grossman
2004-08-30 17:25     ` Ravinandan Arakali
2004-09-13 17:09   ` Ravinandan Arakali
2004-09-17  0:38     ` Jeff Garzik
2004-09-17  0:53       ` Ravinandan Arakali
2004-09-17  0:52         ` Jeff Garzik
2004-09-17  3:07           ` Randy.Dunlap
2004-09-28  0:42           ` Ravinandan Arakali
2004-09-28  3:54             ` Randy.Dunlap
2004-09-28 15:05             ` Jeff Garzik
2004-09-28 17:13               ` Ravinandan Arakali [this message]
2004-10-06 20:14               ` Ravinandan Arakali
2004-10-06 20:09                 ` Jeff Garzik
2004-10-06 20:20                   ` Francois Romieu
2004-10-06 22:52                     ` Jeff Garzik
2004-10-07  1:04                       ` [PATCH 2.6.9-rc2 1/8] S2io: cosmetic changes Ravinandan Arakali
2004-09-17  3:58     ` Patch submission for S2io Xframe driver to 2.6 kernel Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2004-09-13 22:45 Ravinandan Arakali

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='002b01c4a57e$84da0700$a010100a@S2IOtech.com' \
    --to=ravinandan.arakali@s2io.com \
    --cc=jgarzik@pobox.com \
    --cc=leonid.grossman@s2io.com \
    --cc=netdev@oss.sgi.com \
    --cc=raghavendra.koushik@s2io.com \
    --cc=rapuru.sriram@s2io.com \
    /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).