From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kni: fix stack frame size compile error
Date: Thu, 22 Sep 2016 17:44:52 +0200 [thread overview]
Message-ID: <2592566.C9CFSSo88e@xps13> (raw)
In-Reply-To: <20160922144854.1318-1-ferruh.yigit@intel.com>
2016-09-22 15:48, Ferruh Yigit:
> Compile error:
> .../lib/librte_eal/linuxapp/kni/kni_net.c:
> In function ‘kni_net_rx_lo_fifo’:
> .../lib/librte_eal/linuxapp/kni/kni_net.c:331:1:
> error: the frame size of 1056 bytes is larger than 1024 bytes
> [-Werror=frame-larger-than=]
>
> This compile error seen with some compiler / kernel combinations.
>
> Moved some local variables to the kni_dev struct.
>
> Fixes: 8451269e6d7b ("kni: remove continuous memory restriction")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-09-22 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 14:48 Ferruh Yigit
2016-09-22 15:44 ` Thomas Monjalon [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=2592566.C9CFSSo88e@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).