From: Jakub Kicinski <kuba@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
Vladimir Oltean <olteanv@gmail.com>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org
Subject: Re: [net-next:main 26/50] net/ipv4/tcp.c:4673:2: error: call to '__compiletime_assert_1030' declared with 'error' attribute: BUILD_BUG_ON failed: offsetof(struct tcp_sock, __cacheline_group_end__tcp_sock_write_txrx) - offsetofend(struct tcp_sock, __cacheline_group_begin__tcp_sock_...
Date: Thu, 11 Apr 2024 18:37:06 -0700 [thread overview]
Message-ID: <20240411183706.70e5dfcd@kernel.org> (raw)
In-Reply-To: <a59e2164-7159-445e-9f87-fcf6cb4b57d6@gmail.com>
On Thu, 11 Apr 2024 12:21:22 -0700 Florian Fainelli wrote:
> > Florian, does arm32 break a lot? I may not be paying sufficient
> > attention. We can add more build tests but the CPU time we have
> > is unfortunately finite :(
>
> Yes, that is why I mentioned multi_v7_defconfig, you an see the build
> failure with that configuration. Of course Eric fixed it now, thanks!
Would you be willing to type up a bash script along the lines of:
https://github.com/linux-netdev/nipa/blob/main/contest/tests/build-doc.sh
perhaps some inspiration from:
https://github.com/linux-netdev/nipa/blob/main/tests/patch/build_allmodconfig_warn/build_allmodconfig.sh
? (the former runs on the test branches the latter commit by commit)
prev parent reply other threads:[~2024-04-12 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 14:49 [net-next:main 26/50] net/ipv4/tcp.c:4673:2: error: call to '__compiletime_assert_1030' declared with 'error' attribute: BUILD_BUG_ON failed: offsetof(struct tcp_sock, __cacheline_group_end__tcp_sock_write_txrx) - offsetofend(struct tcp_sock, __cacheline_group_begin__tcp_sock_ kernel test robot
2024-04-08 23:06 ` Vladimir Oltean
2024-04-09 5:08 ` Eric Dumazet
2024-04-10 17:28 ` Florian Fainelli
2024-04-10 17:33 ` Eric Dumazet
2024-04-11 1:36 ` Jakub Kicinski
2024-04-11 19:21 ` Florian Fainelli
2024-04-12 1:37 ` Jakub Kicinski [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=20240411183706.70e5dfcd@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olteanv@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.