From: kernel test robot <lkp@intel.com>
To: John Ousterhout <ouster@cs.stanford.edu>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, John Ousterhout <ouster@cs.stanford.edu>
Subject: Re: [PATCH net-next v7 01/14] net: homa: define user-visible API for Homa
Date: Tue, 1 Apr 2025 15:55:50 +0800 [thread overview]
Message-ID: <202504011506.UcytJuoU-lkp@intel.com> (raw)
In-Reply-To: <20250331234548.62070-2-ouster@cs.stanford.edu>
Hi John,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/John-Ousterhout/net-homa-define-user-visible-API-for-Homa/20250401-080339
base: net-next/main
patch link: https://lore.kernel.org/r/20250331234548.62070-2-ouster%40cs.stanford.edu
patch subject: [PATCH net-next v7 01/14] net: homa: define user-visible API for Homa
config: i386-buildonly-randconfig-002-20250401 (https://download.01.org/0day-ci/archive/20250401/202504011506.UcytJuoU-lkp@intel.com/config)
compiler: clang version 20.1.1 (https://github.com/llvm/llvm-project 424c2d9b7e4de40d0804dd374721e6411c27d1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250401/202504011506.UcytJuoU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202504011506.UcytJuoU-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> usr/include/linux/homa.h:179: userspace cannot reference function or variable defined in the kernel
usr/include/linux/homa.h:183: userspace cannot reference function or variable defined in the kernel
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-04-01 7:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250331234548.62070-2-ouster@cs.stanford.edu>]
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=202504011506.UcytJuoU-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ouster@cs.stanford.edu \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox