[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220819191300.0e5e28f1@xps-13>
Date: Fri, 19 Aug 2022 19:13:00 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Alexander Aring <aahringo@...hat.com>
Cc: Alexander Aring <alex.aring@...il.com>,
Stefan Schmidt <stefan@...enfreihafen.org>,
linux-wpan - ML <linux-wpan@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Network Development <netdev@...r.kernel.org>,
David Girault <david.girault@...vo.com>,
Romuald Despres <romuald.despres@...vo.com>,
Frederic Blain <frederic.blain@...vo.com>,
Nicolas Schodet <nico@...fr.eu.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH wpan-next 05/20] net: ieee802154: Define frame types
Hi Alexander,
aahringo@...hat.com wrote on Sun, 10 Jul 2022 22:06:57 -0400:
> Hi,
>
> On Fri, Jul 1, 2022 at 10:36 AM Miquel Raynal <miquel.raynal@...tlin.com> wrote:
> >
> > A 802.15.4 frame can be of different types, here is a definition
> > matching the specification. This enumeration will be soon be used when
> > adding scanning support.
> >
> > Signed-off-by: Miquel Raynal <miquel.raynal@...tlin.com>
> > ---
> > include/net/ieee802154_netdev.h | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/include/net/ieee802154_netdev.h b/include/net/ieee802154_netdev.h
> > index d0d188c3294b..13167851b1c3 100644
> > --- a/include/net/ieee802154_netdev.h
> > +++ b/include/net/ieee802154_netdev.h
> > @@ -69,6 +69,17 @@ struct ieee802154_hdr_fc {
> > #endif
> > };
> >
> > +enum ieee802154_frame_type {
> > + IEEE802154_BEACON_FRAME,
> > + IEEE802154_DATA_FRAME,
> > + IEEE802154_ACKNOWLEDGEMENT_FRAME,
> > + IEEE802154_MAC_COMMAND_FRAME,
> > + IEEE802154_RESERVED_FRAME,
> > + IEEE802154_MULTIPURPOSE_FRAME,
> > + IEEE802154_FRAGMENT_FRAME,
> > + IEEE802154_EXTENDED_FRAME,
> > +};
>
> Please use and extend include/linux/ieee802154.h e.g. IEEE802154_FC_TYPE_DATA.
> I am also not a fan of putting those structs on payload, because there
> can be several problems with it, we should introduce inline helpers to
> check/get each individual fields but... the struct is currently how
> it's implemented.
Ok, I can easily do that.
Thanks,
Miquèl
Powered by blists - more mailing lists