From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] net-next: openvswitch: IPv6: Add IPv6 extension header support
Date: Thu, 06 May 2021 10:03:23 +0800 [thread overview]
Message-ID: <202105060934.AXpcx9gB-lkp@intel.com> (raw)
In-Reply-To: <20210505180808.20505-1-cpp.code.lv@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
Hi Toms,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net/master]
[also build test WARNING on ipsec/master ipvs/master net-next/master linus/master v5.12 next-20210505]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Toms-Atteka/net-next-openvswitch-IPv6-Add-IPv6-extension-header-support/20210506-021045
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git 4c7a94286ef7ac7301d633f17519fb1bb89d7550
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cocci warnings: (new ones prefixed by >>)
>> net/openvswitch/flow.c:378:2-3: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65746 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Toms Atteka <cpp.code.lv@gmail.com>, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, Toms Atteka <cpp.code.lv@gmail.com>
Subject: Re: [PATCH] net-next: openvswitch: IPv6: Add IPv6 extension header support
Date: Thu, 6 May 2021 10:03:23 +0800 [thread overview]
Message-ID: <202105060934.AXpcx9gB-lkp@intel.com> (raw)
In-Reply-To: <20210505180808.20505-1-cpp.code.lv@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Hi Toms,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net/master]
[also build test WARNING on ipsec/master ipvs/master net-next/master linus/master v5.12 next-20210505]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Toms-Atteka/net-next-openvswitch-IPv6-Add-IPv6-extension-header-support/20210506-021045
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git 4c7a94286ef7ac7301d633f17519fb1bb89d7550
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cocci warnings: (new ones prefixed by >>)
>> net/openvswitch/flow.c:378:2-3: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65746 bytes --]
next prev parent reply other threads:[~2021-05-06 2:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 18:08 [PATCH] net-next: openvswitch: IPv6: Add IPv6 extension header support Toms Atteka
2021-05-05 21:47 ` kernel test robot
2021-05-05 21:47 ` kernel test robot
2021-05-06 2:03 ` kernel test robot [this message]
2021-05-06 2:03 ` kernel test robot
2021-05-06 15:41 ` Cpp Code
2021-05-06 15:53 ` Cpp Code
2021-05-06 15:53 ` Cpp Code
2021-05-06 2:03 ` [PATCH] net-next: openvswitch: IPv6: fix semicolon.cocci warnings kernel test robot
2021-05-06 2:03 ` kernel test robot
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=202105060934.AXpcx9gB-lkp@intel.com \
--to=lkp@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.