Linux-parisc archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	 Linux Regressions <regressions@lists.linux.dev>,
	lkft-triage@lists.linaro.org
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>
Subject: arch/parisc/mm/init.c:534:29: error: invalid application of 'sizeof' to incomplete type 'struct shmid64_ds'
Date: Tue, 19 Dec 2023 20:32:42 +0530	[thread overview]
Message-ID: <CA+G9fYvq+wdDhTjR2YkULF-_-nQNPGzCeOON-08EbVyidj-J6w@mail.gmail.com> (raw)

Following build failures noticed on parisc on Linux next-20231219 tag.

parisc:
  build:
    * gcc-11-defconfig - Failed
    * gcc-11-allnoconfig - Failed
    * gcc-11-tinyconfig - Failed

Build error:
arch/parisc/mm/init.c: In function 'mem_init':
arch/parisc/mm/init.c:534:29: error: invalid application of 'sizeof'
to incomplete type 'struct shmid64_ds'
  534 |         BUILD_BUG_ON(sizeof(struct shmid64_ds) != 104);
      |                             ^~~~~~

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Steps to reproduce:

 tuxmake --runtime podman --target-arch parisc --toolchain gcc-11
--kconfig defconfig



Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20231219/testrun/21768759/suite/build/test/gcc-11-defconfig/log
 - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20231219/testrun/21768759/suite/build/tests/



--
Linaro LKFT
https://lkft.linaro.org

             reply	other threads:[~2023-12-19 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 15:02 Naresh Kamboju [this message]
2023-12-19 19:19 ` arch/parisc/mm/init.c:534:29: error: invalid application of 'sizeof' to incomplete type 'struct shmid64_ds' Anders Roxell
2023-12-19 20:48   ` Kent Overstreet
2023-12-19 21:13     ` Anders Roxell

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=CA+G9fYvq+wdDhTjR2YkULF-_-nQNPGzCeOON-08EbVyidj-J6w@mail.gmail.com \
    --to=naresh.kamboju@linaro.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=regressions@lists.linux.dev \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).