[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180514114720.GA25280@yexl-desktop>
Date: Mon, 14 May 2018 19:47:20 +0800
From: Ye Xiaolong <xiaolong.ye@...el.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Cc: kbuild test robot <lkp@...el.com>, Xin Long <lucien.xin@...il.com>,
Neil Horman <nhorman@...driver.com>, netdev@...r.kernel.org,
Vlad Yasevich <vyasevich@...il.com>,
linux-sctp@...r.kernel.org, kbuild-all@...org
Subject: Re: [kbuild-all] [PATCH net-next 2/2] sctp: add
sctp_make_op_error_limited and reuse inner functions
On 05/14, Marcelo Ricardo Leitner wrote:
>On Mon, May 14, 2018 at 03:40:53PM +0800, Ye Xiaolong wrote:
>> >> 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.
>>
>> Do you mean your patchset require MTU refactor patchset as prerequisites?
>
>Yes.
Then it is recommended to use '--base' option of git format-patch, it would record
the base tree info in the first patch or cover letter, 0day bot would apply your
patchset to right base according to it.
Thanks,
Xiaolong
>
>Thanks,
>Marcelo
Powered by blists - more mailing lists