From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] 4.4 steps towards release
Date: Mon, 16 Jan 2023 02:08:01 +0100 (CET) [thread overview]
Message-ID: <1960108615.1128727.1673831281319@webmail.strato.com> (raw)
In-Reply-To: <Y8R5rSX/stuomgBP@duo.ucw.cz>
> On 01/15/2023 11:09 PM CET Pavel Machek <pavel@denx.de> wrote:
> Ok, I'm a bit confused. I remember working these patches, and I do not
> see your sign-offs. If you checked them, I guess I don't need to go
> through them at this point.
>
> | 9cb1ee33e a36e50 .+ | drm/msm/hdmi: check return value after calling platform_get_resource_byname()
> | c132f2ba7 ddbd89 o | swiotlb: fix info leak with DMA_FROM_DEVICE
> | fd97de9c7 901c72 o | Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""
> | 136b47994 190cc8 o | tcp: change source port randomizarion at connect() time
> | 05a12e5c4 c579bd o | tcp: add some entropy in __inet_hash_connect()
> | 576696ed0 b2d057 o | secure_seq: use the 64 bits of the siphash for port offset calculation
> | 2ed413f14 9e9b70 o | tcp: use different parts of the port_offset for index and offset
> | aa7722529 ca7af0 o | tcp: add small random increments to the source port
> | dd82067bd e92614 o | tcp: dynamically allocate the perturb table used by source ports
> | 3c78eea64 4c2c8f o | tcp: increase source port perturb table to 2^16
> | a81a6b204 e81613 o | tcp: drop the hash_32() part from the index calculation
That's a cut-and-paste error on my side, these are in the current release already.
> I'll continue tommorow.
Thanks!
CU
Uli
next prev parent reply other threads:[~2023-01-16 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:53 4.4 steps towards release Pavel Machek
2023-01-10 8:14 ` [cip-dev] " Ulrich Hecht
2023-01-15 22:09 ` Pavel Machek
2023-01-16 1:08 ` Ulrich Hecht [this message]
2023-01-17 20:50 ` Pavel Machek
2023-01-18 5:57 ` Ulrich Hecht
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=1960108615.1128727.1673831281319@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
/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