Re: [nft PATCH] doc: nft.8: Describe iface_type data type

[Phil Sutter <phil@nwl.cc>]

On Tue, Jan 27, 2026 at 11:17:59PM +0100, Florian Westphal wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> > An entry in data-types.txt offers space for a name-value table. Even if
> > one would refer to ARPHRD_*, some names are not derived from the
> > respective macro name and thus not intuitive.
> > 
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > ---
> >  doc/data-types.txt         | 27 +++++++++++++++++++++++++++
> >  doc/primary-expression.txt |  2 --
> >  2 files changed, 27 insertions(+), 2 deletions(-)
> > 
> > diff --git a/doc/data-types.txt b/doc/data-types.txt
> > index e44308b5322cb..0b350effbea68 100644
> > --- a/doc/data-types.txt
> > +++ b/doc/data-types.txt
> > @@ -83,6 +83,33 @@ filter input iifname eth0
> >  filter input iifname "(eth0)"
> >  ----------------------------
> >  
> > +INTERFACE TYPE TYPE
> > +~~~~~~~~~~~~~~~~~~~
> 
> TYPE TYPE?

Yes, sadly. ;)

We also have "ICMP TYPE TYPE" and "ICMPV6 TYPE TYPE" - the types
themselves are called "icmp_type", "icmpv6_type" and "iface_type". So
section titles formed like "<type> type" end up this way. It seems
wrong, but "INTERFACE TYPE" is misleading as the type is not called
"interface" but "interface type".

Maybe we should include the underscores in the title?

Cheers, Phil