[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241002182800.nzk7qqe7zovhuelf@DEN-DL-M70577>
Date: Wed, 2 Oct 2024 18:28:00 +0000
From: Daniel Machon <daniel.machon@...rochip.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Lars Povlsen
<lars.povlsen@...rochip.com>, Steen Hegelund <Steen.Hegelund@...rochip.com>,
<horatiu.vultur@...rochip.com>, <jensemil.schulzostergaard@...rochip.com>,
<UNGLinuxDriver@...rochip.com>, Richard Cochran <richardcochran@...il.com>,
<horms@...nel.org>, <justinstitt@...gle.com>, <gal@...dia.com>,
<aakash.r.menon@...il.com>, <jacob.e.keller@...el.com>,
<netdev@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 06/15] net: sparx5: add constants to match data
> > By "type the code out" - are you saying that we should not be using a macro
> > for accessing the const at all? and rather just:
> >
> > struct sparx5_consts *consts = sparx5->data->consts;
> > consts->some_var
>
> This.
>
> > or pass in the sparx5 pointer to the macro too, which was the concert that
> > Jacob raised.
>
> The implicit arguments are part of the ugliness, and should also go
> away. But in this case the entire macro should go.
Ack.
Will get rid of the macro in v2.
/Daniel
Powered by blists - more mailing lists