From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Xin Long <lucien.xin@gmail.com>
Subject: Re: [PATCH net-next 2/2] sctp: add sctp_make_op_error_limited and reuse inner functions
Date: Mon, 30 Apr 2018 02:34:21 +0000 [thread overview]
Message-ID: <20180430023421.GA4977@localhost.localdomain> (raw)
In-Reply-To: <201804300849.DRgYHLmw%fengguang.wu@intel.com>
On Mon, Apr 30, 2018 at 10:14:06AM +0800, kbuild test robot wrote:
> Hi Marcelo,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Marcelo-Ricardo-Leitner/sctp-allow-sctp_init_cause-to-return-errors/20180430-073613
This URL doesn't work, 404.
> config: x86_64-randconfig-x006-201817 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> net//sctp/sm_make_chunk.c: In function 'sctp_make_op_error_limited':
> >> net//sctp/sm_make_chunk.c:1260:9: error: implicit declaration of function 'sctp_mtu_payload'; did you mean 'sctp_do_peeloff'? [-Werror=implicit-function-declaration]
> size = sctp_mtu_payload(sp, size, sizeof(struct sctp_errhdr));
> ^~~~~~~~~~~~~~~~
> sctp_do_peeloff
> cc1: some warnings being treated as errors
Seems the test didn't pick up the MTU refactor patchset yet.
$ grep sctp/sctp -- net/sctp/sm_make_chunk.c
#include <net/sctp/sctp.h>
$ git grep sctp_mtu_payload -- include/
include/net/sctp/sctp.h:static inline __u32 sctp_mtu_payload(const
struct sctp_sock *sp,
it should be reachable.
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Xin Long <lucien.xin@gmail.com>
Subject: Re: [PATCH net-next 2/2] sctp: add sctp_make_op_error_limited and reuse inner functions
Date: Sun, 29 Apr 2018 23:34:21 -0300 [thread overview]
Message-ID: <20180430023421.GA4977@localhost.localdomain> (raw)
In-Reply-To: <201804300849.DRgYHLmw%fengguang.wu@intel.com>
On Mon, Apr 30, 2018 at 10:14:06AM +0800, kbuild test robot wrote:
> Hi Marcelo,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Marcelo-Ricardo-Leitner/sctp-allow-sctp_init_cause-to-return-errors/20180430-073613
This URL doesn't work, 404.
> config: x86_64-randconfig-x006-201817 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> net//sctp/sm_make_chunk.c: In function 'sctp_make_op_error_limited':
> >> net//sctp/sm_make_chunk.c:1260:9: error: implicit declaration of function 'sctp_mtu_payload'; did you mean 'sctp_do_peeloff'? [-Werror=implicit-function-declaration]
> size = sctp_mtu_payload(sp, size, sizeof(struct sctp_errhdr));
> ^~~~~~~~~~~~~~~~
> sctp_do_peeloff
> cc1: some warnings being treated as errors
Seems the test didn't pick up the MTU refactor patchset yet.
$ grep sctp/sctp -- net/sctp/sm_make_chunk.c
#include <net/sctp/sctp.h>
$ git grep sctp_mtu_payload -- include/
include/net/sctp/sctp.h:static inline __u32 sctp_mtu_payload(const
struct sctp_sock *sp,
it should be reachable.
Marcelo
next prev parent reply other threads:[~2018-04-30 2:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 15:56 [PATCH net-next 0/2] sctp: unify sctp_make_op_error_fixed and sctp_make_op_error_space Marcelo Ricardo Leitner
2018-04-29 15:56 ` Marcelo Ricardo Leitner
2018-04-29 15:56 ` [PATCH net-next 1/2] sctp: allow sctp_init_cause to return errors Marcelo Ricardo Leitner
2018-04-29 15:56 ` Marcelo Ricardo Leitner
2018-04-29 15:56 ` [PATCH net-next 2/2] sctp: add sctp_make_op_error_limited and reuse inner functions Marcelo Ricardo Leitner
2018-04-29 15:56 ` Marcelo Ricardo Leitner
2018-04-30 2:14 ` kbuild test robot
2018-04-30 2:14 ` kbuild test robot
2018-04-30 2:14 ` kbuild test robot
2018-04-30 2:14 ` kbuild test robot
2018-04-30 2:34 ` Marcelo Ricardo Leitner [this message]
2018-04-30 2:34 ` Marcelo Ricardo Leitner
2018-05-14 7:40 ` [kbuild-all] " Ye Xiaolong
2018-05-14 7:40 ` Ye Xiaolong
2018-05-14 11:01 ` Marcelo Ricardo Leitner
2018-05-14 11:01 ` Marcelo Ricardo Leitner
2018-05-14 11:47 ` Ye Xiaolong
2018-05-14 11:47 ` Ye Xiaolong
2018-05-14 12:16 ` Marcelo Ricardo Leitner
2018-05-14 12:16 ` Marcelo Ricardo Leitner
2018-05-15 1:23 ` Ye Xiaolong
2018-05-15 1:23 ` Ye Xiaolong
2018-05-23 22:34 ` Marcelo Ricardo Leitner
2018-05-23 22:34 ` Marcelo Ricardo Leitner
2018-05-01 16:13 ` [PATCH net-next 0/2] sctp: unify sctp_make_op_error_fixed and sctp_make_op_error_space David Miller
2018-05-01 16:13 ` David Miller
2018-05-01 23:28 ` Marcelo Ricardo Leitner
2018-05-01 23:28 ` Marcelo Ricardo Leitner
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=20180430023421.GA4977@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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 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.