public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10
Date: Tue, 09 Jan 2018 21:05:37 +0000	[thread overview]
Message-ID: <1515531937.12097.1.camel@codethink.co.uk> (raw)
In-Reply-To: <20180108105621.osnfazlumesxkwv3@linutronix.de>

On Mon, 2018-01-08 at 11:56 +0100, Sebastian Andrzej Siewior wrote:
> On 2018-01-08 11:13:12 [+0100], Daniel Wagner wrote:
> > Hi Sebastian,
> 
> Hi Daniel,
> 
> > On 01/08/2018 10:33 AM, Sebastian Andrzej Siewior wrote:
> > > 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?
> > 
> > CIP stands for Civil Infrastructure Platform [1]. Ben Hutchings maintains
> > the 4.4.x-cip kernel tree which is a super long stable tree [2].
> 
> So 4.4.x is maintained until Feb, 2022. I assumed that `cip' will take
> over / help Greg with the v4.4 tree and won't include its "own" things.

The 4.4-cip branch is not a regular stable branch.  It includes some
backported hardware enablement and other minor features that aren't
suitable for stable.  I am helping with review for 4.4-stable and
regularly merge it into 4.4-cip, but it's *not* planned for CIP to take
over maintenance of stable branches.  After EOL for 4.4-stable, 4.4-cip 
will get fixes for only the kernel components that CIP members use.

> > > > ? 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.
> > 
> > Okay, I just don't know if Ben wants to add the patch to his tree though.
> 
> If the patch solves the issue then please forward the patch upstream.
> The "normal" v4.4 stable tree is affected by this, too.

4.4-stable doesn't have UBSAN.  Are some other configurations (or
compiler versions) where this code fails to build?  (I'm a bit
surprised that it ever compiled!)

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  parent reply	other threads:[~2018-01-09 21:05 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
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 [this message]
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=1515531937.12097.1.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --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