[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210625060107.14098-1-rocco.yue@mediatek.com>
Date: Fri, 25 Jun 2021 14:01:07 +0800
From: Rocco Yue <rocco.yue@...iatek.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Jonathan Corbet <corbet@....net>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Felix Fietkau <nbd@....name>, John Crispin <john@...ozen.org>,
Sean Wang <sean.wang@...iatek.com>,
Mark Lee <Mark-MC.Lee@...iatek.com>, <netdev@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <bpf@...r.kernel.org>,
<wsd_upstream@...iatek.com>, <chao.song@...iatek.com>,
<kuohong.wang@...iatek.com>, Rocco Yue <rocco.yue@...iatek.com>
Subject: Re: [PATCH 1/4] net: if_arp: add ARPHRD_PUREIP type
> Does changelog mean adding these details to the commit message ?
>
> Yes please.
>
will do.
> > > And are these user-visable flags documented in a man page or something
> > > else somewhere? If not, how does userspace know about them?
> > >
> >
> > There are mappings of these device types value in the libc:
> > "/bionic/libc/kernel/uapi/linux/if_arp.h".
> > userspace can get it from here.
>
> Yes, they will show up in a libc definition, but where is it documented
> in text form what the flag does?
Judging from the changes of ARPHRD_xxx submitted before, I am sorry
I could not find the corresponding doucuments to describe their
respective behaviors in details. Perhaps the best way to understand
their behaviors is to read the code directly.
Thanks,
Rocco
Powered by blists - more mailing lists