From: kernel test robot <lkp@intel.com>
To: Anjali Kulkarni <anjali.k.kulkarni@oracle.com>,
<davem@davemloft.net>, <Liam.Howlett@oracle.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>, <oleg@redhat.com>,
<akpm@linux-foundation.org>, <axboe@kernel.dk>,
<brauner@kernel.org>, <mhocko@suse.com>,
<alexjlzheng@tencent.com>, <willy@infradead.org>,
<michael.christie@oracle.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <shuah@kernel.org>,
<linux-kselftest@vger.kernel.org>, <anjali.k.kulkarni@oracle.com>,
<peili.io@oracle.com>
Subject: Re: [PATCH net-next 2/2] connector/cn_proc: Selftest for threads case
Date: Sun, 22 Sep 2024 09:23:38 +0800 [thread overview]
Message-ID: <Zu9xmkQYUkRhSx9k@rli9-mobl> (raw)
In-Reply-To: <20240920000933.185090-3-anjali.k.kulkarni@oracle.com>
Hi Anjali,
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/Anjali-Kulkarni/connector-cn_proc-Handle-threads-for-proc-connector/20240920-081249
base: net-next/main
patch link: https://lore.kernel.org/r/20240920000933.185090-3-anjali.k.kulkarni%40oracle.com
patch subject: [PATCH net-next 2/2] connector/cn_proc: Selftest for threads case
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240921/202409212201.l94GHFkW-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/r/202409212201.l94GHFkW-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from ../../../../include/uapi/linux/netlink.h:7,
from proc_filter.c:11:
>> ../../../../include/uapi/linux/types.h:10:2: warning: #warning "Attempt to use kernel headers from user space, see https://kernelnewbies.org/KernelHeaders" [-Wcpp]
10 | #warning "Attempt to use kernel headers from user space, see https://kernelnewbies.org/KernelHeaders"
| ^~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-22 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 0:09 [PATCH net-next 0/2] Threads extension for process connector Anjali Kulkarni
2024-09-20 0:09 ` [PATCH net-next 1/2] connector/cn_proc: Handle threads for proc connector Anjali Kulkarni
2024-09-20 11:00 ` Oleg Nesterov
2024-09-20 15:42 ` Anjali Kulkarni
2024-09-20 18:44 ` Oleg Nesterov
2024-09-20 19:39 ` Anjali Kulkarni
2024-09-20 0:09 ` [PATCH net-next 2/2] connector/cn_proc: Selftest for threads case Anjali Kulkarni
2024-09-22 1:23 ` kernel test robot [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=Zu9xmkQYUkRhSx9k@rli9-mobl \
--to=lkp@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexjlzheng@tencent.com \
--cc=anjali.k.kulkarni@oracle.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=michael.christie@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=peili.io@oracle.com \
--cc=shuah@kernel.org \
--cc=willy@infradead.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