From: Jeff Garzik <jeff@garzik.org>
To: Ananda Raju <Ananda.Raju@neterion.com>
Cc: netdev@vger.kernel.org, leonid.grossman@neterion.com,
alicia.pena@neterion.com, ramkrishna.vepa@neterion.com,
sreenivasa.honnur@neterion.com, sriram.rapuru@neterion.com,
sivakumar.subramani@neterion.com, santosh.rastapur@neterion.com
Subject: Re: [PATCH 2.6.20 1/5] s2io: Making LRO and UFO as module loadable parameter.
Date: Wed, 31 Jan 2007 05:17:57 -0500 [thread overview]
Message-ID: <45C06CD5.5030809@garzik.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10701290043110.27317-100000@guinness>
Ananda Raju wrote:
> This patch adds two load parameters napi and ufo. Previously NAPI was
> compilation option with these changes wan enable disable NAPI using load
> parameter. Also we are introducing ufo load parameter to enable/disable
> ufo feature
>
> Signed-off-by: Sivakumar Subramani <sivakumar.subramani@neterion.com>
ACK patches 1-5, but still problems:
1) does not apply to netdev#upstream
2) adds trailing whitespace
[jgarzik@pretzel netdev-2.6]$ git-am --signoff --utf8 /g/tmp/mbox
Applying 's2io: Making LRO and UFO as module loadable parameter.'
Adds trailing whitespace.
.dotest/patch:46: }
Adds trailing whitespace.
.dotest/patch:209:
error: patch failed: drivers/net/s2io.c:6984
error: drivers/net/s2io.c: patch does not apply
Patch failed at 0001.
When you have resolved this problem run "git-am --resolved".
If you would prefer to skip this patch, instead run "git-am --skip".
next prev parent reply other threads:[~2007-01-31 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 5:49 [PATCH 2.6.20 1/5] s2io: Making LRO and UFO as module loadable parameter Ananda Raju
2007-01-31 10:17 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 19:13 Sivakumar Subramani
2007-01-31 18:28 Sivakumar Subramani
2007-02-02 13:22 ` Jeff Garzik
2007-01-31 3:54 Sivakumar Subramani
2007-01-29 6:05 Sivakumar Subramani
2007-01-19 7:31 Ananda Raju
2007-01-23 5:40 ` Jeff Garzik
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=45C06CD5.5030809@garzik.org \
--to=jeff@garzik.org \
--cc=Ananda.Raju@neterion.com \
--cc=alicia.pena@neterion.com \
--cc=leonid.grossman@neterion.com \
--cc=netdev@vger.kernel.org \
--cc=ramkrishna.vepa@neterion.com \
--cc=santosh.rastapur@neterion.com \
--cc=sivakumar.subramani@neterion.com \
--cc=sreenivasa.honnur@neterion.com \
--cc=sriram.rapuru@neterion.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).