[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Daniel Wagner]

Hello CIP RT Folks!

I'm pleased to announce the 4.4.176-cip31-rt23 stable release.

This release is just an update to the new stable 4.4.176-cip31 version
and no RT specific changes have been made.

You can get this release via the git tree at:

  git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git

  branch: linux-4.4.y-cip-rt
  Head SHA1: b51a171ad762ba4a78b0ed0c7ec83fb9f6fb135f

Enjoy!
   Daniel

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Jan Kiszka]

Hi Pavel,

On 29.03.19 12:06, Daniel Wagner wrote:
> Hello CIP RT Folks!
> 
> I'm pleased to announce the 4.4.176-cip31-rt23 stable release.
> 
> This release is just an update to the new stable 4.4.176-cip31 version
> and no RT specific changes have been made.
> 
> You can get this release via the git tree at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
> 
>   branch: linux-4.4.y-cip-rt
>   Head SHA1: b51a171ad762ba4a78b0ed0c7ec83fb9f6fb135f
> 

Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
then to 4.4.182 in order to have SACK fixes in?

Thanks,
Jan

PS: Please make it -rt24 then. ;)

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

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Pavel Machek]

Hi!

> > I'm pleased to announce the 4.4.176-cip31-rt23 stable release.
> > 
> > This release is just an update to the new stable 4.4.176-cip31 version
> > and no RT specific changes have been made.
> > 
> > You can get this release via the git tree at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
> > 
> >   branch: linux-4.4.y-cip-rt
> >   Head SHA1: b51a171ad762ba4a78b0ed0c7ec83fb9f6fb135f
> > 
> 
> Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
> then to 4.4.182 in order to have SACK fixes in?

I'm looking into it. I have -rt-rebase based on
v4.4.179-rt181-cip34-rebase (close to what you want but not quite
there; I can publish it if it would be useful), but duplicating same
result with merges might be tricky.

Best regards,
								Pavel

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190715/7b122d3c/attachment.sig>

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Pavel Machek]

Hi!

> > I'm pleased to announce the 4.4.176-cip31-rt23 stable release.
> > 
> > This release is just an update to the new stable 4.4.176-cip31 version
> > and no RT specific changes have been made.
> > 
> > You can get this release via the git tree at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
> > 
> >   branch: linux-4.4.y-cip-rt
> >   Head SHA1: b51a171ad762ba4a78b0ed0c7ec83fb9f6fb135f
> > 
> 
> Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
> then to 4.4.182 in order to have SACK fixes in?

Do you want 4.4.184, too, which fixes the SACK fixes? :-).

I'm up-to 4.4.179-rt181-cip32.

If I attempt to move forward to 4.4.181-cip3, I get some conflicts in
rather core files.

Auto-merging kernel/cpu.c
CONFLICT (content): Merge conflict in kernel/cpu.c
Auto-merging include/linux/sched.h
CONFLICT (content): Merge conflict in include/linux/sched.h
Auto-merging arch/x86/include/asm/thread_info.h
CONFLICT (content): Merge conflict in

I can attempt something, but I'd feel safer waiting for -stable-rt to
solve it for me.

Best regards,

								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190715/fd9d0465/attachment.sig>

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Daniel Wagner]

>> Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
>> then to 4.4.182 in order to have SACK fixes in?
> 
> Do you want 4.4.184, too, which fixes the SACK fixes? :-).
> 
> I'm up-to 4.4.179-rt181-cip32.
> 
> If I attempt to move forward to 4.4.181-cip3, I get some conflicts in
> rather core files.
> 
> Auto-merging kernel/cpu.c
> CONFLICT (content): Merge conflict in kernel/cpu.c
> Auto-merging include/linux/sched.h
> CONFLICT (content): Merge conflict in include/linux/sched.h
> Auto-merging arch/x86/include/asm/thread_info.h
> CONFLICT (content): Merge conflict in
> 
> I can attempt something, but I'd feel safer waiting for -stable-rt to
> solve it for me.

FWIW, I am updating the stable-rt tree right now. As noted there are a 
couple of merge conflicts ahead. Right now I am testing the result of 
the v4.4.180 merge. So far all looks good and now I am waiting for the 
test results from the CI system. After that I keep merging.

In case you are wondering how the workflow works. We stable-rt 
maintainer merge the latest stable release and make a release if there 
is no merge conflict. If there is a merge conflict, that particular 
stable merge will be released as separate version.  That allows to 
review the merge conflicts more easily.

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Pavel Machek]

Hi!

> >>Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
> >>then to 4.4.182 in order to have SACK fixes in?
> >
> >Do you want 4.4.184, too, which fixes the SACK fixes? :-).
> >
> >I'm up-to 4.4.179-rt181-cip32.
> >
> >If I attempt to move forward to 4.4.181-cip3, I get some conflicts in
> >rather core files.
> >
> >Auto-merging kernel/cpu.c
> >CONFLICT (content): Merge conflict in kernel/cpu.c
> >Auto-merging include/linux/sched.h
> >CONFLICT (content): Merge conflict in include/linux/sched.h
> >Auto-merging arch/x86/include/asm/thread_info.h
> >CONFLICT (content): Merge conflict in
> >
> >I can attempt something, but I'd feel safer waiting for -stable-rt to
> >solve it for me.
> 
> FWIW, I am updating the stable-rt tree right now. As noted there are a
> couple of merge conflicts ahead. Right now I am testing the result of the
> v4.4.180 merge. So far all looks good and now I am waiting for the test
> results from the CI system. After that I keep merging.

Thanks for good news. You have privat CI system, right?

If sources are available somewhere, I can try to help with testing.

Best regards,
								Pavl
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190716/dd18a9fc/attachment.sig>

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Daniel Wagner]

Good Morning,

On 7/16/19 10:14 PM, Pavel Machek wrote:
> Hi!
> 
>>>> Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
>>>> then to 4.4.182 in order to have SACK fixes in?
>>>
>>> Do you want 4.4.184, too, which fixes the SACK fixes? :-).
>>>
>>> I'm up-to 4.4.179-rt181-cip32.
>>>
>>> If I attempt to move forward to 4.4.181-cip3, I get some conflicts in
>>> rather core files.
>>>
>>> Auto-merging kernel/cpu.c
>>> CONFLICT (content): Merge conflict in kernel/cpu.c
>>> Auto-merging include/linux/sched.h
>>> CONFLICT (content): Merge conflict in include/linux/sched.h
>>> Auto-merging arch/x86/include/asm/thread_info.h
>>> CONFLICT (content): Merge conflict in
>>>
>>> I can attempt something, but I'd feel safer waiting for -stable-rt to
>>> solve it for me.
>>
>> FWIW, I am updating the stable-rt tree right now. As noted there are a
>> couple of merge conflicts ahead. Right now I am testing the result of the
>> v4.4.180 merge. So far all looks good and now I am waiting for the test
>> results from the CI system. After that I keep merging.
> 
> Thanks for good news. You have privat CI system, right?

I got a private one at home for development and I am also using the one 
sponsored by LinuxFoundation:

	https://ci-rt.linutronix.de/RT-Test/

I used to push the CIP version for testing to this CI system as well 
(see cip-4.4.y-rt branch). If you are interested to get access to the CI 
system you have to talk to Anna-Maria.

> If sources are available somewhere, I can try to help with testing.

I've just uploaded the v4.4.180-rt182 version. Announcement is coming 
later. I continue with the merging. I keep you updated.

Thanks,
Daniel

[cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23

[Pavel Machek]

Hi!

> > I'm pleased to announce the 4.4.176-cip31-rt23 stable release.
> > 
> > This release is just an update to the new stable 4.4.176-cip31 version
> > and no RT specific changes have been made.
> > 
> > You can get this release via the git tree at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
> > 
> >   branch: linux-4.4.y-cip-rt
> >   Head SHA1: b51a171ad762ba4a78b0ed0c7ec83fb9f6fb135f
> > 
> 
> Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but
> then to 4.4.182 in order to have SACK fixes in?
...
> PS: Please make it -rt24 then. ;)

As -stable-rt was updated (thanks, Daniel!) I now have something. I
pushed the results to the git, I'll run a bit of tests and then we are
ready for release...

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190717/90d8e8d3/attachment.sig>