oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Huyadi <hu.yadi@h3c.com>
To: "'kernel test robot'" <lkp@intel.com>,
	"jmorris@namei.org" <jmorris@namei.org>,
	"serge@hallyn.com" <serge@hallyn.com>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
	"mic@digikod.net" <mic@digikod.net>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-security-module@vger.kernel.org"
	<linux-security-module@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"514118380@qq.com" <514118380@qq.com>
Subject: 回复: [PATCH v3] selftests/landlock:Fix two build issues
Date: Mon, 15 Jan 2024 10:41:32 +0000	[thread overview]
Message-ID: <44bf55ff3e3649c88c5b1daf843a86b5@h3c.com> (raw)
In-Reply-To: <202401151147.T1s11iHJ-lkp@intel.com>


>Hi Hu,
>
>kernel test robot noticed the following build errors:
>
> [auto build test ERROR on shuah-kselftest/next] [also build test ERROR on shuah-kselftest/fixes linus/master v6.7 next-20240112] [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#_base_tree_information]

>url:    https://github.com/intel-lab-lkp/linux/commits/Hu-Yadi/selftests-landlock-Fix-two-build-issues/20240112-151805
>base:   https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
>patch link:    https://lore.kernel.org/r/20240112071245.669-1-hu.yadi%40h3c.com
>patch subject: [PATCH v3] selftests/landlock:Fix two build issues
>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/20240115/202401151147.T1s11iHJ-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/202401151147.T1s11iHJ-lkp@intel.
>| com/
>
>All errors (new ones prefixed by >>):
>

Fix it, and send patch V4 soon.

>>> net_test.c:25:14: error: static declaration of 'gettid' follows 
>>> non-static declaration
>      25 | static pid_t gettid(void)
>         |              ^~~~~~
>   In file included from /usr/include/unistd.h:1218,
>                    from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24,
>                    from /usr/include/signal.h:328,
>                    from /usr/include/x86_64-linux-gnu/sys/wait.h:36,
>                    from common.h:16,
>                    from net_test.c:22:
>   /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: previous declaration of 'gettid' with type '__pid_t(void)' {aka 'int(void)'}
>      34 | extern __pid_t gettid (void) __THROW;
>         |                ^~~~~~
>
>--
>0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2024-01-15 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240112071245.669-1-hu.yadi@h3c.com>
2024-01-15  3:46 ` [PATCH v3] selftests/landlock:Fix two build issues kernel test robot
2024-01-15 10:41   ` Huyadi [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=44bf55ff3e3649c88c5b1daf843a86b5@h3c.com \
    --to=hu.yadi@h3c.com \
    --cc=514118380@qq.com \
    --cc=jmorris@namei.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mic@digikod.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=serge@hallyn.com \
    --cc=shuah@kernel.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).