DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: david.marchand@redhat.com, stephen@networkplumber.org,
	rjarry@redhat.com,  mb@smartsharesystems.com, dev@dpdk.org
Subject: Re: [PATCH] fib: rename configuration flag
Date: Tue, 26 Nov 2024 19:56:54 +0100	[thread overview]
Message-ID: <5888798.QJadu78ljV@thomas> (raw)
In-Reply-To: <20241126171840.1499453-1-vladimir.medvedkin@intel.com>

26/11/2024 18:18, Vladimir Medvedkin:
> Rename RTE_FIB_F_NETWORK_ORDER with RTE_FIB_F_LOOKUP_NETWORK_ORDER to
> explicitly indicate that it is only used in lookup.
> 
> Fixes: e194f3cd5685 ("fib: lookup IPv4 address in network order")
> 
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>

Applied, thanks.




      reply	other threads:[~2024-11-26 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 17:18 Vladimir Medvedkin
2024-11-26 18:56 ` Thomas Monjalon [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=5888798.QJadu78ljV@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=rjarry@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=vladimir.medvedkin@intel.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.
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 NNTP newsgroup(s).