From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@denx.de (Pavel Machek) Date: Mon, 15 Jul 2019 15:43:36 +0200 Subject: [cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23 In-Reply-To: References: <20190329110611.1B897500722@mail.monom.org> Message-ID: <20190715134336.GB16268@amd> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org 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: