From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Stefan Schmidt <stefan@datenfreihafen.org>,
	linux-wpan - ML <linux-wpan@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	David Girault <david.girault@qorvo.com>,
	Romuald Despres <romuald.despres@qorvo.com>,
	Frederic Blain <frederic.blain@qorvo.com>,
	Nicolas Schodet <nico@ni.fr.eu.org>
Subject: Re: [PATCH wpan-next v2 2/2] net: ieee802154: Move the address structure earlier and provide a kdoc
Date: Mon, 31 Jan 2022 11:46:45 +0100	[thread overview]
Message-ID: <20220131114645.341d61e9@xps13> (raw)
In-Reply-To: <CAB_54W7KOjBys4aY5Ky3N3zmSGHnW2cvfag2cubD4cMvrkHY3A@mail.gmail.com>
Hi Alexander,
alex.aring@gmail.com wrote on Sun, 30 Jan 2022 16:09:00 -0500:
> Hi,
> 
> On Fri, Jan 28, 2022 at 6:20 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > From: David Girault <david.girault@qorvo.com>
> >
> > Move the address structure earlier in the cfg802154.h header in order to
> > use it in subsequent additions. Give this structure a header to better
> > explain its content.
> >
> > Signed-off-by: David Girault <david.girault@qorvo.com>
> > [miquel.raynal@bootlin.com: Isolate this change from a bigger commit and
> >                             reword the comment]
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > ---
> >  include/net/cfg802154.h | 28 +++++++++++++++++++---------
> >  1 file changed, 19 insertions(+), 9 deletions(-)
> >
> > diff --git a/include/net/cfg802154.h b/include/net/cfg802154.h
> > index 4491e2724ff2..0b8b1812cea1 100644
> > --- a/include/net/cfg802154.h
> > +++ b/include/net/cfg802154.h
> > @@ -29,6 +29,25 @@ struct ieee802154_llsec_key_id;
> >  struct ieee802154_llsec_key;
> >  #endif /* CONFIG_IEEE802154_NL802154_EXPERIMENTAL */
> >
> > +/**
> > + * struct ieee802154_addr - IEEE802.15.4 device address
> > + * @mode: Address mode from frame header. Can be one of:
> > + *        - @IEEE802154_ADDR_NONE
> > + *        - @IEEE802154_ADDR_SHORT
> > + *        - @IEEE802154_ADDR_LONG
> > + * @pan_id: The PAN ID this address belongs to
> > + * @short_addr: address if @mode is @IEEE802154_ADDR_SHORT
> > + * @extended_addr: address if @mode is @IEEE802154_ADDR_LONG
> > + */
> > +struct ieee802154_addr {
> > +       u8 mode;
> > +       __le16 pan_id;
> > +       union {
> > +               __le16 short_addr;
> > +               __le64 extended_addr;
> > +       };
> > +};
> > +
> >  struct cfg802154_ops {
> >         struct net_device * (*add_virtual_intf_deprecated)(struct wpan_phy *wpan_phy,
> >                                                            const char *name,
> > @@ -277,15 +296,6 @@ static inline void wpan_phy_net_set(struct wpan_phy *wpan_phy, struct net *net)
> >         write_pnet(&wpan_phy->_net, net);
> >  }
> >
> > -struct ieee802154_addr {
> > -       u8 mode;
> > -       __le16 pan_id;
> > -       union {
> > -               __le16 short_addr;
> > -               __le64 extended_addr;
> > -       };
> > -};
> > -  
> 
> I don't see the sense of moving this around? Is there a compilation
> warning/error?
Not yet but we will need to move this structure around soon. This
commit is like a 'preparation' step for the changes coming later.
I can move this later if you prefer.
Thanks,
Miquèl
next prev parent reply	other threads:[~2022-01-31 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 11:20 [PATCH wpan-next v2 0/2] ieee802154: Internal moves Miquel Raynal
2022-01-28 11:20 ` [PATCH wpan-next v2 1/2] net: ieee802154: Move the IEEE 802.15.4 Kconfig main entries Miquel Raynal
2022-01-30 20:47   ` Alexander Aring
2022-01-30 21:07   ` Alexander Aring
2022-01-31 13:46     ` Miquel Raynal
2022-01-31 22:57       ` Alexander Aring
2022-01-28 11:20 ` [PATCH wpan-next v2 2/2] net: ieee802154: Move the address structure earlier and provide a kdoc Miquel Raynal
2022-01-30 21:09   ` Alexander Aring
2022-01-31 10:46     ` Miquel Raynal [this message]
2022-01-31 14:09       ` Miquel Raynal
2022-01-31 22:43         ` Alexander Aring
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=20220131114645.341d61e9@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=david.girault@qorvo.com \
    --cc=frederic.blain@qorvo.com \
    --cc=kuba@kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nico@ni.fr.eu.org \
    --cc=romuald.despres@qorvo.com \
    --cc=stefan@datenfreihafen.org \
    --cc=thomas.petazzoni@bootlin.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).