From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
David Taylor <davidt@yadt.co.uk>
Subject: [PATCH] doc: Trivial fix for reuseaddr-priority
Date: Mon, 15 Jul 2024 10:43:07 +1000 [thread overview]
Message-ID: <20240715004307.41501-1-david@gibson.dropbear.id.au> (raw)
This test program checks for particular behaviour regardless of order of
operations. So, we step through the test with all possible orders for
a number of different of parts. Or at least, we're supposed to, a copy
pasta error led to using the same order for two things which should be
independent.
Fixes: 299c40750 ("doc: Add program to document and test assumptions...")
Reported-by: David Taylor <davidt@yadt.co.uk>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
doc/platform-requirements/reuseaddr-priority.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/platform-requirements/reuseaddr-priority.c b/doc/platform-requirements/reuseaddr-priority.c
index 644553f8..701b6fff 100644
--- a/doc/platform-requirements/reuseaddr-priority.c
+++ b/doc/platform-requirements/reuseaddr-priority.c
@@ -222,7 +222,7 @@ static void check_all_orders(void)
for (k = 0; k < norders; k++)
for (l = 0; l < norders; l++)
check_one_order(orders[i], orders[j],
- orders[j], orders[l]);
+ orders[k], orders[l]);
}
int main(int argc, char *argv[])
--
@@ -222,7 +222,7 @@ static void check_all_orders(void)
for (k = 0; k < norders; k++)
for (l = 0; l < norders; l++)
check_one_order(orders[i], orders[j],
- orders[j], orders[l]);
+ orders[k], orders[l]);
}
int main(int argc, char *argv[])
--
2.45.2
next reply other threads:[~2024-07-15 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 0:43 David Gibson [this message]
2024-07-15 16:57 ` [PATCH] doc: Trivial fix for reuseaddr-priority Stefano Brivio
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=20240715004307.41501-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=davidt@yadt.co.uk \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).