All of lore.kernel.org
 help / color / mirror / Atom feed
From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23
Date: Mon, 15 Jul 2019 14:24:13 +0200	[thread overview]
Message-ID: <20190715122413.GA16268@amd> (raw)
In-Reply-To: <a86d4f19-790d-58ab-94b4-523a759d87b4@siemens.com>

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>

  reply	other threads:[~2019-07-15 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 11:06 [cip-dev] [ANNOUNCE] 4.4.176-cip31-rt23 Daniel Wagner
2019-07-11  8:47 ` Jan Kiszka
2019-07-15 12:24   ` Pavel Machek [this message]
2019-07-15 13:43   ` Pavel Machek
2019-07-16 14:09     ` Daniel Wagner
2019-07-16 20:14       ` Pavel Machek
2019-07-17  6:46         ` Daniel Wagner
2019-07-17 12:16   ` Pavel Machek

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=20190715122413.GA16268@amd \
    --to=pavel@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.