From: David Miller <davem@davemloft.net>
To: ariele@broadcom.com
Cc: davem@davemlof.net, netdev@vger.kernel.org, eilong@broadcom.com
Subject: Re: [PATCH net-next] bnx2x: stop using on-stack napi struct
Date: Wed, 02 Nov 2011 01:00:47 -0400 (EDT) [thread overview]
Message-ID: <20111102.010047.414830511681971161.davem@davemloft.net> (raw)
In-Reply-To: <1320163450.11011.19.camel@lb-tlvb-ariel.il.broadcom.com>
From: "Ariel Elior" <ariele@broadcom.com>
Date: Tue, 1 Nov 2011 18:04:10 +0200
> Napi structure was allocated on stack to hold temporary value of copied
> fastpath. This can be avoided by using the source fastpath as a
> scratchpad thus saving stack space and code.
> Signed-off-by: Ariel Elior <ariele@broadcom.com>
> Signed-off-by: Eilon Greenstein <eilong@broadcom.com>
Your patch has been severely corrupted by your email client.
I'm sure your colleagues at Broadcom can help you fix this
so that you can submit this patch properly. :-)
prev parent reply other threads:[~2011-11-02 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 16:04 [PATCH net-next] bnx2x: stop using on-stack napi struct Ariel Elior
2011-11-02 5:00 ` David Miller [this message]
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=20111102.010047.414830511681971161.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariele@broadcom.com \
--cc=davem@davemlof.net \
--cc=eilong@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).