From: Li Zhijian <zhijianx.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH net-next] lwtunnel: be STRICT to validate the new LWTUNNEL_IP(6)_OPTS
Date: Mon, 25 Nov 2019 15:05:58 +0800 [thread overview]
Message-ID: <8f6c19ee-f975-c367-dfcd-1b0cdd47f3e7@intel.com> (raw)
In-Reply-To: <CADvbK_cBwFDsdE89VugbnKvELE2zUzWN2Tr0ds81efWfv-MtMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]
On 11/25/19 2:43 PM, Xin Long wrote:
> On Mon, Nov 25, 2019 at 2:39 PM Li Zhijian<zhijianx.li@intel.com> wrote:
>> On 11/24/19 8:31 PM, Xin Long wrote:
>>
>> On Sat, Nov 23, 2019 at 10:11 PM kbuild test robot<lkp@intel.com> wrote:
>>
>> Hi Xin,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on net/master]
>> [also build test ERROR on v5.4-rc8]
>> [cannot apply to net-next/master next-20191122]
>> [if your patch is applied to the wrong git tree, please drop us a note to help
>> improve the system. BTW, we also suggest to use '--base' option to specify the
>> base tree in git format-patch, please seehttps://stackoverflow.com/a/37406982]
>>
>> url:https://github.com/0day-ci/linux/commits/Xin-Long/lwtunnel-be-STRICT-to-validate-the-new-LWTUNNEL_IP-6-_OPTS/20191123-204806
>> base:https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git 5b1d9c17a3e0c16e1c9adf9c8a89f2735cb6dff8
>>
>> This patch shouldn't be applied to net.git without:
>>
>> commit 4ece477870774698e6e73d5821a3dd1605ca123b
>> Author: Xin Long<lucien.xin@gmail.com>
>> Date: Wed Nov 6 17:01:05 2019 +0800
>>
>> lwtunnel: add options setting and dumping for geneve
>>
>> Hi,
>>
>> May i know which tree/branch you are basing on for the patch "[PATCH] lwtunnel: be STRICT to validate the new LWTUNNEL_IP(6)_OPTS"
>> Your inputs could be helpful for us to improve our kbuild robot continuously.
>>
>> As the mentioned above, the kbuild robot failed to apply to net-next/master which i have checked that
>> 4ece477870774698e6e73d5821a3dd1605ca123b was already included
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> on this tree, it worked to me.
thanks. i knew what happened i think.
this patch have been merged into net-next/master already, so this is a negative report.
Thanks
Zhijian
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3250 bytes --]
prev parent reply other threads:[~2019-11-25 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 10:11 [PATCH net-next] lwtunnel: be STRICT to validate the new LWTUNNEL_IP(6)_OPTS Xin Long
2019-11-21 19:48 ` David Miller
2019-11-23 14:11 ` kbuild test robot
2019-11-24 12:31 ` Xin Long
2019-11-25 0:33 ` Rong Chen
2019-11-25 6:38 ` Li Zhijian
2019-11-25 6:43 ` Xin Long
2019-11-25 7:05 ` Li Zhijian [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=8f6c19ee-f975-c367-dfcd-1b0cdd47f3e7@intel.com \
--to=zhijianx.li@intel.com \
--cc=kbuild-all@lists.01.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.