From: kbuild test robot <fengguang.wu@intel.com>
To: Maor Gottlieb <maorg@mellanox.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Moni Shoua <monis@mellanox.com>,
Matan Barak <matanb@mellanox.com>
Subject: drivers/infiniband/hw/mlx5/main.c:1162:1: warning: the frame size of 1108 bytes is larger than 1024 bytes
Date: Fri, 15 Jan 2016 02:14:07 +0800 [thread overview]
Message-ID: <201601150205.7KODcgsA%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7fdec82af6a9e190e53d07a1463d2a9ac49a8750
commit: 038d2ef87572757861a177b19f9d489def2c48b8 IB/mlx5: Add flow steering support
date: 3 days ago
config: i386-randconfig-h0-01150100 (attached as .config)
reproduce:
git checkout 038d2ef87572757861a177b19f9d489def2c48b8
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
drivers/infiniband/hw/mlx5/main.c: In function 'create_flow_rule':
>> drivers/infiniband/hw/mlx5/main.c:1162:1: warning: the frame size of 1108 bytes is larger than 1024 bytes [-Wframe-larger-than=]
}
^
vim +1162 drivers/infiniband/hw/mlx5/main.c
1146 dst);
1147
1148 if (IS_ERR(handler->rule)) {
1149 err = PTR_ERR(handler->rule);
1150 goto free;
1151 }
1152
1153 handler->prio = ft_prio - dev->flow_db.prios;
1154
1155 ft_prio->flow_table = ft;
1156 free:
1157 if (err)
1158 kfree(handler);
1159 kfree(match_c);
1160 kfree(match_v);
1161 return err ? ERR_PTR(err) : handler;
> 1162 }
1163
1164 enum {
1165 LEFTOVERS_MC,
1166 LEFTOVERS_UC,
1167 };
1168
1169 static struct mlx5_ib_flow_handler *create_leftovers_rule(struct mlx5_ib_dev *dev,
1170 struct mlx5_ib_flow_prio *ft_prio,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 27207 bytes --]
reply other threads:[~2016-01-14 18:16 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=201601150205.7KODcgsA%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=matanb@mellanox.com \
--cc=monis@mellanox.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).