From: nick <xerofoify@gmail.com>
To: jeffrey.t.kirsher@intel.com
Cc: linux.nics@intel.com, e1000-devel@lists.sourceforge.net,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
linux-kernel@vger.kernel.org, john.ronciak@intel.com,
netdev@vger.kernel.org
Subject: Possible Bug Found with Build Warning?
Date: Fri, 05 Dec 2014 15:55:59 -0500 [thread overview]
Message-ID: <54821BDF.1060607@gmail.com> (raw)
Greetings Jeff and the other developers at Intel,
I seem to be getting this error message,
drivers/net/ethernet/intel/i40e/i40e_debugfs.c: In function ‘i40e_dbg_dump_desc’:
drivers/net/ethernet/intel/i40e/i40e_debugfs.c:855:1: warning: the frame size of 8192 bytes is larger than 2048 bytes [-Wframe-larger-than=]
}
^
when building the kernel for the last few weeks for my other patches. As you can tell it states issues with the frame size being larger then 2048 bytes. I am wondering is this a issue as the struct is allocated only 2048 bytes of system memory per frame or is this just a mistake on me reading the warning.
Regards Nick
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
reply other threads:[~2014-12-05 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54821BDF.1060607@gmail.com \
--to=xerofoify@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.