From: bigeasy@linutronix.de (Sebastian Andrzej Siewior)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10
Date: Mon, 8 Jan 2018 10:33:50 +0100 [thread overview]
Message-ID: <20180108093350.lxjocaxlvrmjwpav@linutronix.de> (raw)
In-Reply-To: <b4cf2728-0d0c-5128-d007-818e66da5613@siemens.com>
On 2018-01-02 12:56:11 [+0100], Daniel Wagner wrote:
> The release is based on the Linux 4.4.75-rt88 version. That is I
> applied the -rt88 patch on the 4.4.75-cip6 kernel and merged in all
> CIP releases.
what is cip6?
> https://ci-rt.linutronix.de/RT-Test/kbuild.jsp?id=112
>
> Some of the builds are failing (allmodconfig), though it
> doesn't look cip-rt specific, eg:
>
> kernel/utilities/compiletest-runner at 2/build/../include/linux/compiler.h:484 call to ?__compiletime_assert_150? declared with attribute error: BUILD_BUG_ON failed: hw_flag_names[NUM_IEEE80211_HW_FLAGS] != (void *)0x1
>
> Not sure how to handle those. IIRC, we don't support allmodconfig.
yes but adding
68920c973254 ("net/mac80211/debugfs.c: prevent build failure with
CONFIG_UBSAN=y")
could solve the issue.
Sebastian
next prev parent reply other threads:[~2018-01-08 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 11:56 [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10 Daniel Wagner
2018-01-02 12:29 ` Daniel Wagner
2018-01-08 9:33 ` Sebastian Andrzej Siewior [this message]
2018-01-08 10:13 ` Daniel Wagner
2018-01-08 10:56 ` Sebastian Andrzej Siewior
2018-01-08 11:45 ` Daniel Wagner
2018-01-08 14:06 ` Jan Kiszka
2018-01-08 14:56 ` Agustín Benito Bethencourt
2018-01-09 21:05 ` Ben Hutchings
2018-01-09 21:31 ` Hindman, Gavin
2018-01-10 17:32 ` Sebastian Andrzej Siewior
2018-01-11 8:07 ` Daniel Wagner
2018-01-11 16:51 ` Ben Hutchings
2018-01-17 9:18 ` Daniel Wagner
2018-01-10 9:04 ` Daniel Wagner
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=20180108093350.lxjocaxlvrmjwpav@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=cip-dev@lists.cip-project.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