From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <lkp@intel.com>
Cc: <kbuild-all@lists.01.org>, <kuniyu@amazon.com>,
<linux-mm@kvack.org>, <pabeni@redhat.com>
Subject: Re: [linux-next:master 6765/11208] unix_connect.c:115:55: error:
Date: Mon, 18 Jul 2022 09:11:14 -0700 [thread overview]
Message-ID: <20220718161114.18550-1-kuniyu@amazon.com> (raw)
In-Reply-To: <202207182205.FrkMeDZT-lkp@intel.com>
From: kernel test robot <lkp@intel.com>
Date: Mon, 18 Jul 2022 22:32:11 +0800
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 036ad6daa8f0fd357af7f50f9da58539eaa6f68c
> commit: e95ab1d852897a0b697cd0fb609d496ce97fff3a [6765/11208] selftests: net: af_unix: Test connect() with different netns.
> reproduce: make O=/tmp/kselftest -C tools/testing/selftests
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> Note: the linux-next/master HEAD 036ad6daa8f0fd357af7f50f9da58539eaa6f68c builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> unix_connect.c: In function 'unix_connect_test':
> >> unix_connect.c:115:55: error: expected identifier before '(' token
> 115 | #define offsetof(type, member) ((size_t)&((type *)0)->(member))
> | ^
I'll fix this.
The change suggested by checkpatch seems to be the root cause.
Best regards,
Kuniyuki
> unix_connect.c:128:19: note: in expansion of macro 'offsetof'
> 128 | addrlen = offsetof(struct sockaddr_un, sun_path) + variant->len;
> | ^~~~~~~~
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
prev parent reply other threads:[~2022-07-18 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 14:32 [linux-next:master 6765/11208] unix_connect.c:115:55: error: expected identifier before '(' token kernel test robot
2022-07-18 16:11 ` Kuniyuki Iwashima [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=20220718161114.18550-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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