[ANNOUNCE] Linux 4.4.15-cip15-rt10

[ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Hello CIP RT Folks!
	
I'm pleased to announce the Linux 4.4.15-cip15-rt10 stable release.
	
You can get this release via the git tree at:
	
  git://git.kernel.org/pub/scm/linux/kernel/git/wagi/linux-cip-rt.git
  https://git.kernel.org/pub/scm/linux/kernel/git/wagi/linux-cip-rt.git
	
  branch: linux-4.4.y-cip-rt
  Head SHA1: 6c97018d1d4626e21b5233eb28e607e412c79ebe

Currently, I don't have uploaded the patches, because I need to figure
out how this works on kernel.org.
	
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.

Note we got via the stable tree the new RT pull/push logic
from upstream cb1831a83e54 ("sched/rt: Simplify the IPI based RT
balancing logic").

I spend quite a while to get a baseline configuration working and 
the testing up and running.  I have a BeagleBone Black and a MinnowBoard
Turbot as test target. On the BBB, cyclictest reports reasonable
numbers, though not the MinnowBoard Turbot. It seems the bios/uefi
or so is eating CPU time. The exact same kernel works on different
x86 hardware just fine. 

Furthermore, I let the kernel run on the Real-Time Linux Continuous
Integration servers:

  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@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.

Next steps are improving my tests and identifying which 4.4.${x}-rt${y}
changes should be added to the cip-rt kernel.

Thanks,
Daniel

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Hello CIP RT Folks!
	
I'm pleased to announce the Linux 4.4.15-cip15-rt10 stable release.
	
You can get this release via the git tree at:
	
  git://git.kernel.org/pub/scm/linux/kernel/git/wagi/linux-cip-rt.git
  https://git.kernel.org/pub/scm/linux/kernel/git/wagi/linux-cip-rt.git
	
  branch: linux-4.4.y-cip-rt
  Head SHA1: 6c97018d1d4626e21b5233eb28e607e412c79ebe

Currently, I don't have uploaded the patches, because I need to figure
out how this works on kernel.org.
	
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.

Note we got via the stable tree the new RT pull/push logic
from upstream cb1831a83e54 ("sched/rt: Simplify the IPI based RT
balancing logic").

I spend quite a while to get a baseline configuration working and 
the testing up and running.  I have a BeagleBone Black and a MinnowBoard
Turbot as test target. On the BBB, cyclictest reports reasonable
numbers, though not the MinnowBoard Turbot. It seems the bios/uefi
or so is eating CPU time. The exact same kernel works on different
x86 hardware just fine. 

Furthermore, I let the kernel run on the Real-Time Linux Continuous
Integration servers:

  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.

Next steps are improving my tests and identifying which 4.4.${x}-rt${y}
changes should be added to the cip-rt kernel.

Thanks,
Daniel

Re: [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

On 01/02/2018 12:56 PM, Daniel Wagner wrote:
> Hello CIP RT Folks!
> 	
> I'm pleased to announce the Linux 4.4.15-cip15-rt10 stable release.

Damn, not awake yet, it should read 4.4.105-cip15-rt10

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

On 01/02/2018 12:56 PM, Daniel Wagner wrote:
> Hello CIP RT Folks!
> 	
> I'm pleased to announce the Linux 4.4.15-cip15-rt10 stable release.

Damn, not awake yet, it should read 4.4.105-cip15-rt10

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Sebastian Andrzej Siewior]

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@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

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Sebastian Andrzej Siewior]

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

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Hi Sebastian,

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].

>>   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@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.

Thanks,
Daniel

[1] https://www.cip-project.org/
[2] https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Hi Sebastian,

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].

>>   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.

Thanks,
Daniel

[1] https://www.cip-project.org/
[2] https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Sebastian Andrzej Siewior]

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.

> >>   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@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.

> Thanks,
> Daniel

Sebastian

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Sebastian Andrzej Siewior]

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.

> >>   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.

> Thanks,
> Daniel

Sebastian

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

On 01/08/2018 11:56 AM, Sebastian Andrzej Siewior wrote:
>>>>     kernel/utilities/compiletest-runner@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.

Ah, I misunderstood you first. I'll picked the patch and let it run
through the ci system now and forward it to Greg if it solved the issue.

Thanks,
Daniel

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

On 01/08/2018 11:56 AM, Sebastian Andrzej Siewior wrote:
>>>>     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.

Ah, I misunderstood you first. I'll picked the patch and let it run
through the ci system now and forward it to Greg if it solved the issue.

Thanks,
Daniel

Re: [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Jan Kiszka]

On 2018-01-08 11:56, 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.

CIP includes a number of additional mainline backports (mostly around
SoC/board support and security), so it already deviates from vanilla
LTS. It's also aiming at a stricter QA than LTS.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Jan Kiszka]

On 2018-01-08 11:56, 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.

CIP includes a number of additional mainline backports (mostly around
SoC/board support and security), so it already deviates from vanilla
LTS. It's also aiming at a stricter QA than LTS.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Agustín Benito Bethencourt]

Hi Sebastian,

On Monday, 8 January 2018 10:56:22 WET 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.

Main CIP kernel policies can be found in the wiki: https://
wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance

> 
> > >>   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/compil
> > >>     er.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.
> 
> > Thanks,
> > Daniel
> 
> Sebastian
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev


-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Ben Hutchings]

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@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.

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Ben Hutchings]

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.

RE: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Hindman, Gavin]

Sorry for the top-post.  Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users.  Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way?   Maybe it just needs a clearer header, if we think it should stay on rt-users?

Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?  

-gavin

> -----Original Message-----
> From: linux-rt-users-owner@vger.kernel.org [mailto:linux-rt-users-
> owner@vger.kernel.org] On Behalf Of Ben Hutchings
> Sent: Tuesday, January 09, 2018 1:06 PM
> To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>; Daniel Wagner
> <daniel.wagner@siemens.com>
> Cc: cip-dev@lists.cip-project.org; linux-rt-users <linux-rt-
> users@vger.kernel.org>
> Subject: Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10
> 
> 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@2/build/../include/l
> > > > > > > > > inux/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.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Hindman, Gavin]

Sorry for the top-post.  Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users.  Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way?   Maybe it just needs a clearer header, if we think it should stay on rt-users?

Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?  

-gavin

> -----Original Message-----
> From: linux-rt-users-owner at vger.kernel.org [mailto:linux-rt-users-
> owner at vger.kernel.org] On Behalf Of Ben Hutchings
> Sent: Tuesday, January 09, 2018 1:06 PM
> To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>; Daniel Wagner
> <daniel.wagner@siemens.com>
> Cc: cip-dev at lists.cip-project.org; linux-rt-users <linux-rt-
> users at vger.kernel.org>
> Subject: Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10
> 
> 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/l
> > > > > > > > > inux/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.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the
> body of a message to majordomo at vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Hi Ben,

>>>>>   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@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!)

The problem was introduced by 30686bf7f5b3 ("mac80211: convert HW flags
to unsigned long bitmap"). The only LTS kernel which is missing the
68920c973254 ("net/mac80211/debugfs.c: prevent build failure with
CONFIG_UBSAN=y") fix is the 4.4. The other don't have 30686bf7f5b3, e.g.
4.1, or have 30686bf7f5b3 and 68920c973254, e.g. 4.9.

I've sent 68920c973254 to stable for inclusion into 4.4.

	https://www.spinics.net/lists/stable/msg209228.html

Thanks,
Daniel

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Hi Ben,

>>>>> ? 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!)

The problem was introduced by 30686bf7f5b3 ("mac80211: convert HW flags
to unsigned long bitmap"). The only LTS kernel which is missing the
68920c973254 ("net/mac80211/debugfs.c: prevent build failure with
CONFIG_UBSAN=y") fix is the 4.4. The other don't have 30686bf7f5b3, e.g.
4.1, or have 30686bf7f5b3 and 68920c973254, e.g. 4.9.

I've sent 68920c973254 to stable for inclusion into 4.4.

	https://www.spinics.net/lists/stable/msg209228.html

Thanks,
Daniel

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Sebastian Andrzej Siewior]

On 2018-01-09 21:31:34 [+0000], Hindman, Gavin wrote:
> Sorry for the top-post.  Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users.  Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way?   Maybe it just needs a clearer header, if we think it should stay on rt-users?

I think the announcement was just fine. Now I do know what it does and
what will happen after Greg decides to put 4.4 EOL.

A pointer to [0] as part of the announcement might be help full. In the
end I think it should remain on rt-users since Steven won't continue
doing 4.4 stable. So Daniel's 4.4-RT on top of the CIP tree will be the
only source of a maintained 4.4-RT tree.

[0] wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance

> Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?  

So what do have in mind? Moving v4.4-RT over to the "No longer
maintained PREEMPT_RT versions" section and adding a new one with
"related projects" where we add the 4.4-cip-rt tree?
Daniel: you have the release currently in a git tree within his "user"
namespace and did not upload it to k.o. Do you plan upload it to the
stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
folder on k.o.? If so we might just add a link to the cip wiki next to
4.4 and be done with it.
Other suggestions?

> -gavin

Sebastian

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Sebastian Andrzej Siewior]

On 2018-01-09 21:31:34 [+0000], Hindman, Gavin wrote:
> Sorry for the top-post.  Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users.  Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way?   Maybe it just needs a clearer header, if we think it should stay on rt-users?

I think the announcement was just fine. Now I do know what it does and
what will happen after Greg decides to put 4.4 EOL.

A pointer to [0] as part of the announcement might be help full. In the
end I think it should remain on rt-users since Steven won't continue
doing 4.4 stable. So Daniel's 4.4-RT on top of the CIP tree will be the
only source of a maintained 4.4-RT tree.

[0] wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance

> Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?  

So what do have in mind? Moving v4.4-RT over to the "No longer
maintained PREEMPT_RT versions" section and adding a new one with
"related projects" where we add the 4.4-cip-rt tree?
Daniel: you have the release currently in a git tree within his "user"
namespace and did not upload it to k.o. Do you plan upload it to the
stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
folder on k.o.? If so we might just add a link to the cip wiki next to
4.4 and be done with it.
Other suggestions?

> -gavin

Sebastian

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Good morning everyone,

On 01/10/2018 06:32 PM, Sebastian Andrzej Siewior wrote:
> On 2018-01-09 21:31:34 [+0000], Hindman, Gavin wrote:
>> Sorry for the top-post.  Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users.  Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way?   Maybe it just needs a clearer header, if we think it should stay on rt-users?
> 
> I think the announcement was just fine. Now I do know what it does and
> what will happen after Greg decides to put 4.4 EOL.
> 
> A pointer to [0] as part of the announcement might be help full. In the
> end I think it should remain on rt-users since Steven won't continue
> doing 4.4 stable. So Daniel's 4.4-RT on top of the CIP tree will be the
> only source of a maintained 4.4-RT tree.
> 
> [0] wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
> 
>> Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?  
> 
> So what do have in mind? Moving v4.4-RT over to the "No longer
> maintained PREEMPT_RT versions" section and adding a new one with
> "related projects" where we add the 4.4-cip-rt tree?

Steven is handing over the 4.4 to me (*). So I'll maintain the 4.4-rt
and 4.4-cip-rt. I'll expect that they wont differ too much. Famous last
words.

> Daniel: you have the release currently in a git tree within his "user"
> namespace and did not upload it to k.o. Do you plan upload it to the
> stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
> folder on k.o.? If so we might just add a link to the cip wiki next to
> 4.4 and be done with it.

Steven will ask the k.o folks to give me permission to upload to
projects/rt/4.4. In short nothing should change for 4.4-rt support as
long Greg is releasing 4.4.

As for 4.4-cip(-rt), it might make sense to have a project/cip shared
folder with the 4.4-cip and 4.4-cip-rt tree.

Ben, what's your stand on this?

Thanks,
Daniel

(*) I finally figured out the last pieces how to do a release and
upload to k.o.

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

Good morning everyone,

On 01/10/2018 06:32 PM, Sebastian Andrzej Siewior wrote:
> On 2018-01-09 21:31:34 [+0000], Hindman, Gavin wrote:
>> Sorry for the top-post.  Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users.  Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way?   Maybe it just needs a clearer header, if we think it should stay on rt-users?
> 
> I think the announcement was just fine. Now I do know what it does and
> what will happen after Greg decides to put 4.4 EOL.
> 
> A pointer to [0] as part of the announcement might be help full. In the
> end I think it should remain on rt-users since Steven won't continue
> doing 4.4 stable. So Daniel's 4.4-RT on top of the CIP tree will be the
> only source of a maintained 4.4-RT tree.
> 
> [0] wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
> 
>> Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?  
> 
> So what do have in mind? Moving v4.4-RT over to the "No longer
> maintained PREEMPT_RT versions" section and adding a new one with
> "related projects" where we add the 4.4-cip-rt tree?

Steven is handing over the 4.4 to me (*). So I'll maintain the 4.4-rt
and 4.4-cip-rt. I'll expect that they wont differ too much. Famous last
words.

> Daniel: you have the release currently in a git tree within his "user"
> namespace and did not upload it to k.o. Do you plan upload it to the
> stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
> folder on k.o.? If so we might just add a link to the cip wiki next to
> 4.4 and be done with it.

Steven will ask the k.o folks to give me permission to upload to
projects/rt/4.4. In short nothing should change for 4.4-rt support as
long Greg is releasing 4.4.

As for 4.4-cip(-rt), it might make sense to have a project/cip shared
folder with the 4.4-cip and 4.4-cip-rt tree.

Ben, what's your stand on this?

Thanks,
Daniel

(*) I finally figured out the last pieces how to do a release and
upload to k.o.

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Ben Hutchings]

On Thu, 2018-01-11 at 09:07 +0100, Daniel Wagner wrote:
> Good morning everyone,
> 
> On 01/10/2018 06:32 PM, Sebastian Andrzej Siewior wrote:
[...]
> > Daniel: you have the release currently in a git tree within his "user"
> > namespace and did not upload it to k.o. Do you plan upload it to the
> > stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
> > folder on k.o.? If so we might just add a link to the cip wiki next to
> > 4.4 and be done with it.
> 
> Steven will ask the k.o folks to give me permission to upload to
> projects/rt/4.4. In short nothing should change for 4.4-rt support as
> long Greg is releasing 4.4.
> 
> As for 4.4-cip(-rt), it might make sense to have a project/cip shared
> folder with the 4.4-cip and 4.4-cip-rt tree.
> 
> Ben, what's your stand on this?

No-one's asked for tarballs and patches, so I don't really want to add
that step to the release process.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Ben Hutchings]

On Thu, 2018-01-11 at 09:07 +0100, Daniel Wagner wrote:
> Good morning everyone,
> 
> On 01/10/2018 06:32 PM, Sebastian Andrzej Siewior wrote:
[...]
> > Daniel: you have the release currently in a git tree within his "user"
> > namespace and did not upload it to k.o. Do you plan upload it to the
> > stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
> > folder on k.o.? If so we might just add a link to the cip wiki next to
> > 4.4 and be done with it.
> 
> Steven will ask the k.o folks to give me permission to upload to
> projects/rt/4.4. In short nothing should change for 4.4-rt support as
> long Greg is releasing 4.4.
> 
> As for 4.4-cip(-rt), it might make sense to have a project/cip shared
> folder with the 4.4-cip and 4.4-cip-rt tree.
> 
> Ben, what's your stand on this?

No-one's asked for tarballs and patches, so I don't really want to add
that step to the release process.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

Re: [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

On 01/11/2018 05:51 PM, Ben Hutchings wrote:
> On Thu, 2018-01-11 at 09:07 +0100, Daniel Wagner wrote:
>> Good morning everyone,
>>
>> On 01/10/2018 06:32 PM, Sebastian Andrzej Siewior wrote:
> [...]
>>> Daniel: you have the release currently in a git tree within his "user"
>>> namespace and did not upload it to k.o. Do you plan upload it to the
>>> stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
>>> folder on k.o.? If so we might just add a link to the cip wiki next to
>>> 4.4 and be done with it.
>>
>> Steven will ask the k.o folks to give me permission to upload to
>> projects/rt/4.4. In short nothing should change for 4.4-rt support as
>> long Greg is releasing 4.4.
>>
>> As for 4.4-cip(-rt), it might make sense to have a project/cip shared
>> folder with the 4.4-cip and 4.4-cip-rt tree.
>>
>> Ben, what's your stand on this?
> 
> No-one's asked for tarballs and patches, so I don't really want to add
> that step to the release process.

Fair enough ;)

[cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10

[Daniel Wagner]

On 01/11/2018 05:51 PM, Ben Hutchings wrote:
> On Thu, 2018-01-11 at 09:07 +0100, Daniel Wagner wrote:
>> Good morning everyone,
>>
>> On 01/10/2018 06:32 PM, Sebastian Andrzej Siewior wrote:
> [...]
>>> Daniel: you have the release currently in a git tree within his "user"
>>> namespace and did not upload it to k.o. Do you plan upload it to the
>>> stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
>>> folder on k.o.? If so we might just add a link to the cip wiki next to
>>> 4.4 and be done with it.
>>
>> Steven will ask the k.o folks to give me permission to upload to
>> projects/rt/4.4. In short nothing should change for 4.4-rt support as
>> long Greg is releasing 4.4.
>>
>> As for 4.4-cip(-rt), it might make sense to have a project/cip shared
>> folder with the 4.4-cip and 4.4-cip-rt tree.
>>
>> Ben, what's your stand on this?
> 
> No-one's asked for tarballs and patches, so I don't really want to add
> that step to the release process.

Fair enough ;)