public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] flow: fix wrong macro name in comments
Date: Wed, 7 May 2025 12:10:07 +1000	[thread overview]
Message-ID: <aBrA_5AOrV2TWL53@zatzit> (raw)
In-Reply-To: <20250506141325.185455-1-lvivier@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

On Tue, May 06, 2025 at 04:13:25PM +0200, Laurent Vivier wrote:
> The maximum number of flow macro name is FLOW_MAX, not MAX_FLOW.
> 
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
>  flow.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/flow.c b/flow.c
> index c5718e3c7bf7..6a5c8aa439c2 100644
> --- a/flow.c
> +++ b/flow.c
> @@ -81,7 +81,7 @@ static_assert(ARRAY_SIZE(flow_proto) == FLOW_NUM_TYPES,
>   *
>   * Free cluster list
>   *    flow_first_free gives the index of the first (lowest index) free cluster.
> - *    Each free cluster has the index of the next free cluster, or MAX_FLOW if
> + *    Each free cluster has the index of the next free cluster, or FLOW_MAX if
>   *    it is the last free cluster.  Together these form a linked list of free
>   *    clusters, in strictly increasing order of index.
>   *

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-05-07  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 14:13 [PATCH] flow: fix wrong macro name in comments Laurent Vivier
2025-05-07  2:10 ` David Gibson [this message]
2025-05-08 14:54 ` 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=aBrA_5AOrV2TWL53@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    /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).