From: kbuild test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: kbuild-all@01.org, "David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>,
Soheil Hassas Yeganeh <soheil@google.com>,
Van Jacobson <vanj@google.com>, Jerry Chu <hkchu@google.com>
Subject: Re: [PATCH net-next] tcp: internal implementation for pacing
Date: Tue, 16 May 2017 13:57:04 +0800 [thread overview]
Message-ID: <201705161323.MPIbat79%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170516034318.9913-1-edumazet@google.com>
[-- Attachment #1: Type: text/plain, Size: 3207 bytes --]
Hi Eric,
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Eric-Dumazet/tcp-internal-implementation-for-pacing/20170516-115441
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
include/net/sock.h:476: warning: No description found for parameter 'sk_tsq_flags'
>> include/net/sock.h:476: warning: No description found for parameter 'sk_pacing_status'
include/net/sock.h:476: warning: No description found for parameter '__sk_flags_offset'
include/net/sock.h:476: warning: No description found for parameter 'sk_uid'
drivers/net/phy/phy.c:259: warning: No description found for parameter 'features'
drivers/net/phy/phy.c:259: warning: Excess function parameter 'feature' description in 'phy_lookup_setting'
drivers/net/phy/phy.c:259: warning: No description found for parameter 'features'
drivers/net/phy/phy.c:259: warning: Excess function parameter 'feature' description in 'phy_lookup_setting'
vim +/sk_pacing_status +476 include/net/sock.h
^1da177e4 Linus Torvalds 2005-04-16 460 struct socket *sk_socket;
^1da177e4 Linus Torvalds 2005-04-16 461 void *sk_user_data;
d5f642384 Alexey Dobriyan 2008-11-04 462 #ifdef CONFIG_SECURITY
^1da177e4 Linus Torvalds 2005-04-16 463 void *sk_security;
d5f642384 Alexey Dobriyan 2008-11-04 464 #endif
2a56a1fec Tejun Heo 2015-12-07 465 struct sock_cgroup_data sk_cgrp_data;
baac50bbc Johannes Weiner 2016-01-14 466 struct mem_cgroup *sk_memcg;
^1da177e4 Linus Torvalds 2005-04-16 467 void (*sk_state_change)(struct sock *sk);
676d23690 David S. Miller 2014-04-11 468 void (*sk_data_ready)(struct sock *sk);
^1da177e4 Linus Torvalds 2005-04-16 469 void (*sk_write_space)(struct sock *sk);
^1da177e4 Linus Torvalds 2005-04-16 470 void (*sk_error_report)(struct sock *sk);
^1da177e4 Linus Torvalds 2005-04-16 471 int (*sk_backlog_rcv)(struct sock *sk,
^1da177e4 Linus Torvalds 2005-04-16 472 struct sk_buff *skb);
^1da177e4 Linus Torvalds 2005-04-16 473 void (*sk_destruct)(struct sock *sk);
ef456144d Craig Gallek 2016-01-04 474 struct sock_reuseport __rcu *sk_reuseport_cb;
a4298e452 Eric Dumazet 2016-04-01 475 struct rcu_head sk_rcu;
^1da177e4 Linus Torvalds 2005-04-16 @476 };
^1da177e4 Linus Torvalds 2005-04-16 477
98acdc088 Eric Dumazet 2017-05-15 478 enum sk_pacing {
98acdc088 Eric Dumazet 2017-05-15 479 SK_PACING_NONE = 0,
98acdc088 Eric Dumazet 2017-05-15 480 SK_PACING_NEEDED = 1,
98acdc088 Eric Dumazet 2017-05-15 481 SK_PACING_FQ = 2,
98acdc088 Eric Dumazet 2017-05-15 482 };
98acdc088 Eric Dumazet 2017-05-15 483
559835ea7 Pravin B Shelar 2013-09-24 484 #define __sk_user_data(sk) ((*((void __rcu **)&(sk)->sk_user_data)))
:::::: The code at line 476 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6564 bytes --]
prev parent reply other threads:[~2017-05-16 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 3:43 [PATCH net-next] tcp: internal implementation for pacing Eric Dumazet
2017-05-16 3:49 ` Soheil Hassas Yeganeh
2017-05-16 5:57 ` kbuild test robot [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=201705161323.MPIbat79%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hkchu@google.com \
--cc=kbuild-all@01.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=vanj@google.com \
--cc=ycheng@google.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