From: kernel test robot <rong.a.chen@intel.com>
To: Sharath Chandra Vurukala <sharathv@codeaurora.org>,
davem@davemloft.net, kuba@kernel.org, elder@kernel.org,
cpratapa@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org,
Sharath Chandra Vurukala <sharathv@codeaurora.org>
Subject: Re: [PATCH net-next v6 3/3] net: ethernet: rmnet: Add support for MAPv5 egress packets
Date: Thu, 27 May 2021 11:01:41 +0800 [thread overview]
Message-ID: <20210527030141.GU2687475@shao2-debian> (raw)
In-Reply-To: <1622040882-27526-4-git-send-email-sharathv@codeaurora.org>
Hi Sharath,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Sharath-Chandra-Vurukala/net-qualcomm-rmnet-Enable-Mapv5/20210526-225721
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git e4e92ee78702b13ad55118d8b66f06e1aef62586
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>
includecheck warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c: linux/bitfield.h is included more than once.
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
next prev parent reply other threads:[~2021-05-27 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 14:54 [PATCH net-next v6 0/3] net: qualcomm: rmnet: Enable Mapv5 Sharath Chandra Vurukala
2021-05-26 14:54 ` [PATCH net-next v6 1/3] docs: networking: Add documentation for MAPv5 Sharath Chandra Vurukala
2021-05-26 14:54 ` [PATCH net-next v6 2/3] net: ethernet: rmnet: Support for ingress MAPv5 checksum offload Sharath Chandra Vurukala
2021-05-26 14:54 ` [PATCH net-next v6 3/3] net: ethernet: rmnet: Add support for MAPv5 egress packets Sharath Chandra Vurukala
2021-05-27 3:01 ` kernel test robot [this message]
2021-05-27 3:02 ` [RFC PATCH] net: ethernet: rmnet: fix duplicated inclusion 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=20210527030141.GU2687475@shao2-debian \
--to=rong.a.chen@intel.com \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sharathv@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).