From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/setsockopt05: associate receiver with destination address
Date: Thu, 27 Aug 2020 13:55:53 -0400 (EDT) [thread overview]
Message-ID: <368170331.10374593.1598550953564.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <452994585.10362765.1598543893067.JavaMail.zimbra@redhat.com>
----- Original Message -----
> Hi,
> I assume that cycling through different source ports prevented the issue?
Yes, it did, it ran fine over night.
>
> Reviewed-by: Martin Doucha <mdoucha@suse.cz>
Pushed.
Thanks,
Jan
prev parent reply other threads:[~2020-08-27 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 12:10 [LTP] [PATCH] syscalls/setsockopt05: associate receiver with destination address Jan Stancek
2020-08-24 14:42 ` Martin Doucha
2020-08-24 15:01 ` Jan Stancek
2020-08-24 15:21 ` Martin Doucha
2020-08-24 16:11 ` Jan Stancek
2020-08-25 9:43 ` Martin Doucha
2020-08-25 13:38 ` Jan Stancek
2020-08-26 10:08 ` Martin Doucha
2020-08-26 10:20 ` Martin Doucha
2020-08-26 10:39 ` [LTP] [PATCH] " Martin Doucha
2020-08-27 12:14 ` [LTP] [PATCH v2] " Jan Stancek
2020-08-27 15:55 ` Martin Doucha
2020-08-27 15:58 ` Jan Stancek
2020-08-27 17:55 ` Jan Stancek [this message]
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=368170331.10374593.1598550953564.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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